erofs: fix broken illustration in documentation

Illustration was broken after ReST conversion by accident.
(checked by 'make SPHINXDIRS="filesystems" htmldocs')

Link: https://lore.kernel.org/r/20210510162506.28637-1-xiang@kernel.org
Fixes: e66d8631ddb3 ("docs: filesystems: convert erofs.txt to ReST")
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Signed-off-by: Gao Xiang <xiang@kernel.org>
This commit is contained in:
Gao Xiang 2021-05-11 00:25:05 +08:00
parent 6efb943b86
commit 1b55767dfd

View File

@ -175,7 +175,7 @@ may not. All metadatas can be now observed in two different spaces (views):
Each share xattr can also be directly found by the following formula: Each share xattr can also be directly found by the following formula:
xattr offset = xattr_blkaddr * block_size + 4 * xattr_id xattr offset = xattr_blkaddr * block_size + 4 * xattr_id
:: ::
|-> aligned by 4 bytes |-> aligned by 4 bytes
+ xattr_blkaddr blocks |-> aligned with 4 bytes + xattr_blkaddr blocks |-> aligned with 4 bytes
@ -204,7 +204,6 @@ algorithm (could refer to the related source code).
\ | * could have \ | * could have
\ | trailing '\0' \ | trailing '\0'
\________________________| nameoff0 \________________________| nameoff0
Directory block Directory block
Note that apart from the offset of the first filename, nameoff0 also indicates Note that apart from the offset of the first filename, nameoff0 also indicates
@ -216,21 +215,21 @@ Compression
Currently, EROFS supports 4KB fixed-sized output transparent file compression, Currently, EROFS supports 4KB fixed-sized output transparent file compression,
as illustrated below:: as illustrated below::
|---- Variant-Length Extent ----|-------- VLE --------|----- VLE ----- |<- variable-sized extent ->|<- VLE ->|
clusterofs clusterofs clusterofs clusterofs clusterofs clusterofs
| | | logical data | | |
_________v_______________________________v_____________________v_______________ _________v_________________________________v_______________________v________
... | . | | . | | . | ... ... | . | | . | | . ...
____|____.________|_____________|________.____|_____________|__.__________|____ ____|____._________|______________|________.___ _|______________|__.________
|-> cluster <-|-> cluster <-|-> cluster <-|-> cluster <-|-> cluster <-| |-> lcluster <-|-> lcluster <-|-> lcluster <-|-> lcluster <-|
size size size size size size size size size . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
_______._____________._____________._____________._____________________ _______.______________.______________.______________._________________
... | | | | ... physical data ... | | | | ...
_______|_____________|_____________|_____________|_____________________ _______|______________|______________|______________|_________________
|-> cluster <-|-> cluster <-|-> cluster <-| |-> pcluster <-|-> pcluster <-|-> pcluster <-|
size size size size size size
Currently each on-disk physical cluster can contain 4KB (un)compressed data Currently each on-disk physical cluster can contain 4KB (un)compressed data