From: Chris Mason <chris.mason@oracle.com>
To: Alexander Piavlo <piavka@cs.bgu.ac.il>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: error during umuont after set-default with 2.6.34-rc2
Date: Mon, 22 Mar 2010 09:38:58 -0400 [thread overview]
Message-ID: <20100322133858.GB32521@think> (raw)
In-Reply-To: <201003212045.o2LKjBgg002162@indigo.cs.bgu.ac.il>
On Sun, Mar 21, 2010 at 10:45:11PM +0200, Alexander Piavlo wrote:
> Hi,
> trying the new btrfs tool and set-default with 2.6.34-rc2 i hit the the
> following problem:
>
> mkfs.btrfs -d single /dev/sys/btrfs
> mount -t btrfs /dev/sys/btrfs /btrfs
> btrfs subvolume create /btrfs/newroot
> mkdir /btrfs/newroot/.btrfs
> btrfs subvolume set-default 256 /btrfs
> umount /btrfs
> mount -t btrfs /dev/sys/btrfs /btrfs
>
> up till now everything works ok
>
> A question How do i access or mount the original root of btrfs? Which
> tree id does it have?
> It would be great if "btrfs subvolume list ..." would also list the
> original root.
>
> I guessed I need to use 0, so i tried:
> mount -t btrfs -o subvol=0 /dev/sys/btrfs /btrfs/.btrfs
> and:
> mount -t btrfs -o subvol=. /dev/sys/btrfs /btrfs/.btrfs
> but in both cases it mounted the newroot subvolume with id 256 under
> /btrfs/.btrfs
>
> So I tried setting the original root back with:
> btrfs subvolume set-default 0 /btrfs
Looks like set-default needs to understand 0 means use the old default,
I'll add this in.
btrfs subvolume set-default 5 /btrfs
or mount -o subvolid=0 /dev/xxx /mnt
or mount -o subvolid=5 /dev/xxx /mnt
-chris
next prev parent reply other threads:[~2010-03-22 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 20:45 error during umuont after set-default with 2.6.34-rc2 Alexander Piavlo
2010-03-21 20:58 ` Piavlo
2010-03-22 13:38 ` Chris Mason [this message]
2010-03-22 20:25 ` Piavlo
2010-03-23 15:10 ` Chris Mason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100322133858.GB32521@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=piavka@cs.bgu.ac.il \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.