mirror of
https://github.com/kdave/btrfs-progs
synced 2025-03-23 03:16:29 +00:00
btrfs-progs: doc: clarify toplevel subvolid
Signed-off-by: Shriramana Sharma <samjnaa@gmail.com> Signed-off-by: David Sterba <dsterba@suse.cz>
This commit is contained in:
parent
005c470888
commit
73362471f3
@ -31,7 +31,7 @@ When `mount`(8) using 'subvol' or 'subvolid' mount option, one can access
|
||||
files/directories/subvolumes inside it, but nothing in parent subvolumes.
|
||||
|
||||
Also every btrfs filesystem has a default subvolume as its initially top-level
|
||||
subvolume, whose subvolume id is 5(FS_TREE).
|
||||
subvolume, whose subvolume id is 5. (0 is also acceptable as an alias.)
|
||||
|
||||
A btrfs snapshot is much like a subvolume, but shares its data(and metadata)
|
||||
with other subvolume/snapshot. Due to the capabilities of COW, modifications
|
||||
@ -166,7 +166,7 @@ sleep N seconds between checks (default: 1)
|
||||
|
||||
EXIT STATUS
|
||||
-----------
|
||||
*btrfs subvolume* returns a zero exit status if it succeeds. Non zero is
|
||||
*btrfs subvolume* returns a zero exit status if it succeeds. A non-zero value is
|
||||
returned in case of failure.
|
||||
|
||||
AVAILABILITY
|
||||
|
Loading…
Reference in New Issue
Block a user