Skip to content

Commit

Permalink
Fix a ridiculous number of typos
Browse files Browse the repository at this point in the history
  • Loading branch information
PhracturedBlue committed Apr 1, 2024
1 parent f63e621 commit 623bc71
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -155,7 +155,7 @@ These options are the same regardless of whether you use them with the
the file. An attempt to move the file to that branch will occur
(keeping all metadata possible) and if successful the original is
unlinked and the write retried. (default: false, true = mfs)
* **inodecalc=passthrough|path-hash|devino-hash|baepath-hash|hybrid-hash|basehybrid-hash**:
* **inodecalc=passthrough|path-hash|devino-hash|basepath-hash|hybrid-hash|basehybrid-hash**:
Selects the inode calculation algorithm. (default: hybrid-hash)
* **dropcacheonclose=BOOL**: When a file is requested to be closed
call `posix_fadvise` on it first to instruct the kernel that we no
Expand Down Expand Up @@ -444,10 +444,10 @@ covering different usecases.
different file or files move out of band but will present the same
inode for underlying files that do too.
* devino-hash32: 32bit version of devino-hash.
* basepath-hash: Hashes the underlying-device root-director along with
* basepath-hash: Hashes the branch base path along with
the inode of the underlying entry. This has a similar purpose to
devino-hash, but by using the path instead of the device-id, the inodes
will be gauranteed to be stablee across reboots. Useful for back or
will be gauranteed to be stable across reboots. Useful for backup or
deduplication systems that rely on a static inode. Note that if the
root directory is below the mountpoint of the underlying storage,
duplicate inodes are possible.
Expand Down

0 comments on commit 623bc71

Please sign in to comment.