diff mbox

root subvol id is 0 or 5?

Message ID CAH-HCWW+dWbiGMNJuOExdy_NudQjPvZ4APp56++zK_k-4VSkaQ@mail.gmail.com (mailing list archive)
State New, archived
Headers show

Commit Message

Shriramana Sharma Nov. 30, 2014, 1:42 p.m. UTC
On Sun, Nov 30, 2014 at 7:08 PM, Shriramana Sharma <samjnaa@gmail.com> wrote:
>
> So why 5 and not just 0 which seems a logical choice? On top of this,
> one needs to alias 0 to 5!

Attached patch clarifying this in the documentation. (Should have done
this with the previous mail. Sorry for multiple mails.)

Comments

David Sterba Feb. 27, 2015, 4:50 p.m. UTC | #1
On Sun, Nov 30, 2014 at 07:12:46PM +0530, Shriramana Sharma wrote:
> On Sun, Nov 30, 2014 at 7:08 PM, Shriramana Sharma <samjnaa@gmail.com> wrote:
> >
> > So why 5 and not just 0 which seems a logical choice? On top of this,
> > one needs to alias 0 to 5!
> 
> Attached patch clarifying this in the documentation. (Should have done
> this with the previous mail. Sorry for multiple mails.)
> 
> -- 
> Shriramana Sharma ???????????? ????????????

> From 54387ff2155423d990b5a9aca95315fe6e649303 Mon Sep 17 00:00:00 2001
> From: Shriramana Sharma <samjnaa@gmail.com>
> Date: Sun, 30 Nov 2014 19:11:39 +0530
> Subject: [PATCH 2/2] btrfs subvolume doc clarifications

Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff mbox

Patch

From 54387ff2155423d990b5a9aca95315fe6e649303 Mon Sep 17 00:00:00 2001
From: Shriramana Sharma <samjnaa@gmail.com>
Date: Sun, 30 Nov 2014 19:11:39 +0530
Subject: [PATCH 2/2] btrfs subvolume doc clarifications

---
 Documentation/btrfs-subvolume.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/btrfs-subvolume.txt b/Documentation/btrfs-subvolume.txt
index 1360aba..34abdef 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
-- 
2.1.3