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

doc: fix formatting

Browse Source 
fix misnomer and some formatting

Signed-off-by: Alexander Fougner <fougner89@gmail.com>
This commit is contained in:
Alexander Fougner 2022-12-29 16:48:54 +01:00
parent 787768043d
commit d69daae411
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -303,12 +303,12 @@ replicas we're supposed to keep.
\subsection{Reflink}
bcachefs supports reflink, similarly to other filesystems with the same feature.
cp --reflink will create a copy that shares the underlying storage. Reading from
that file will become slightly slower - the extent pointing to that data is
moved to the reflink btree (with a refcount added) and in the extents btree we
leave a key that points to the indirect extent in the reflink btree, meaning
that we now have to do two btree lookups to read from that data instead of just
one.
\texttt{cp --reflink} will create a copy that shares the underlying storage.
Reading from that file will become slightly slower - the extent pointing to that
data is moved to the reflink btree (with a refcount added) and in the extents
btree we leave a key that points to the indirect extent in the reflink btree,
meaning that we now have to do two btree lookups to read from that data instead
of just one.
\subsection{Inline data extents}
@ -383,7 +383,7 @@ bcachefs format --compression=lz4 \
\subsection{Mounting}
To mount a multi device filesystem, there are two options. You can specify all
component devices, separated by hyphens, e.g.
component devices, separated by colons, e.g.
\begin{quote} \begin{verbatim}
mount -t bcachefs /dev/sda:/dev/sdb:/dev/sdc /mnt
\end{verbatim} \end{quote}
@ -395,7 +395,7 @@ replay happens automatically, and diagnostic messages in the dmesg log will
indicate whether recovery was from clean or unclean shutdown.
The \texttt{-o degraded} option will allow a filesystem to be mounted without
all the the devices, but will fail if data would be missing. The
all the devices, but will fail if data would be missing. The
\texttt{-o very\_degraded} can be used to attempt mounting when data would be
missing.