alex/bcachefs-tools
1
0
Fork 0
mirror of https://github.com/koverstreet/bcachefs-tools.git synced 2025-02-23 00:00:02 +03:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

doc: correct some spelling errors

Browse Source
This commit is contained in:
PowerUser64 2024-08-09 21:36:42 -07:00
parent 495a54c03b
commit 5b4ee5cf7b
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/bcachefs-principles-of-operation.tex
View File

@ -394,7 +394,7 @@ The following subcommands exist for managing subvolumes and snapshots:
existing subvolume existing subvolume
\end{itemize} \end{itemize}
A subvolume can also be deleting with a normal rmdir after deleting all the A subvolume can also be deleted with a normal rmdir after deleting all the
contents, as with \texttt{rm -rf}. Still to be implemented: read-only snapshots, contents, as with \texttt{rm -rf}. Still to be implemented: read-only snapshots,
recursive snapshot creation, and a method for recursively listing subvolumes. recursive snapshot creation, and a method for recursively listing subvolumes.
@ -505,8 +505,8 @@ the \texttt{journal\_reclaim\_delay} parameter, with a default of 100
milliseconds. milliseconds.
The journal should be sized sufficiently that bursts of activity do not fill up The journal should be sized sufficiently that bursts of activity do not fill up
the journal too quickly; also, a larger journal mean that we can queue up larger the journal too quickly; also, a larger journal means that we can queue up
btree writes. The \texttt{bcachefs device resize-journal} can be used for larger btree writes. The \texttt{bcachefs device resize-journal} can be used for
resizing the journal on disk on a particular device - it can be used on a resizing the journal on disk on a particular device - it can be used on a
mounted or unmounted filesystem. mounted or unmounted filesystem.
@ -578,8 +578,8 @@ ensuring that checksums are valid, fixing bitrot when a valid copy can be found.
Most bcachefs options can be set filesystem wide, and a significant subset can Most bcachefs options can be set filesystem wide, and a significant subset can
also be set on inodes (files and directories), overriding the global defaults. also be set on inodes (files and directories), overriding the global defaults.
Filesystem wide options may be set when formatting, when mounting, or at runtime Filesystem wide options may be set when formatting, when mounting, or at runtime
via \texttt{/sys/fs/bcachefs/<uuid>/options/}. When set at runtime via sysfs the via \texttt{/sys/fs/bcachefs/<uuid>/options/}. When set at runtime via sysfs,
persistent options in the superblock are updated as well; when options are the persistent options in the superblock are updated as well; when options are
passed as mount parameters the persistent options are unmodified. passed as mount parameters the persistent options are unmodified.
\subsection{File and directory options} \subsection{File and directory options}
@ -593,8 +593,8 @@ inherited attributes to change we fail the rename with -EXDEV, causing userspace
to do the rename file by file so that inherited attributes stay consistent. to do the rename file by file so that inherited attributes stay consistent.
Inode options are available as extended attributes. The options that have been Inode options are available as extended attributes. The options that have been
explicitly set are available under the \texttt{bcachefs} namespace, and the effective explicitly set are available under the \texttt{bcachefs} namespace, and the
options (explicitly set and inherited options) are available under the effective options (explicitly set and inherited options) are available under the
\texttt{bcachefs\_effective} namespace. Examples of listing options with the \texttt{bcachefs\_effective} namespace. Examples of listing options with the
getfattr command: getfattr command: