diff options
| author | Shriramana Sharma <samjnaa@gmail.com> | 2014-11-30 19:12:46 +0530 |
|---|---|---|
| committer | David Sterba <dsterba@suse.cz> | 2015-02-27 17:48:08 +0100 |
| commit | 73362471f33cd1406b09b9600228be9fc8aef710 (patch) | |
| tree | 8db6dcbad3ff09404b0ba9dc9ce162acc59e340e /Documentation/btrfs-subvolume.txt | |
| parent | 005c470888ac2c04ba9263845d0ed3b19e9e6c69 (diff) | |
btrfs-progs: doc: clarify toplevel subvolid
Signed-off-by: Shriramana Sharma <samjnaa@gmail.com>
Signed-off-by: David Sterba <dsterba@suse.cz>
Diffstat (limited to 'Documentation/btrfs-subvolume.txt')
| -rw-r--r-- | Documentation/btrfs-subvolume.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/btrfs-subvolume.txt b/Documentation/btrfs-subvolume.txt index b0ae030e..3dd5289b 100644 --- a/Documentation/btrfs-subvolume.txt +++ b/Documentation/btrfs-subvolume.txt @@ -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 |