From: Wang Shilong <wangshilong1991@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Hugo Mills <hugo@carfax.org.uk>,
Giuseppe Fierro <giuseppe@fierro.org>,
linux-btrfs@vger.kernel.org
Subject: Re: Btrfs prog
Date: Wed, 4 Sep 2013 22:37:58 +0800 [thread overview]
Message-ID: <5E29539F-9625-488E-AD90-A72A37DF20BD@gmail.com> (raw)
In-Reply-To: <5144EC24-48E9-4AC9-8005-F0A3FA18164A@colorremedies.com>
Hello Chris,
>
> On Sep 4, 2013, at 3:32 PM, Hugo Mills <hugo@carfax.org.uk> wrote:
>
>>> If I would like to show the subvolume, i get
>>>
>>>> gspe@jura:/mnt$ sudo btrfs subvolume list /
>>>> gspe@jura:/mnt$
>>>
>>> nothing is shown!!!
>>
>> Try using the -a option. It got added a while ago, and has been a
>> complete pain in the neck ever since…
>
> What does -a do?
>
> I recall with older versions of btrfs-progs that if a subvolume was mounted, btrfs subvol list would only list subvolumes under the one that was mounted, not all subvolumes on the volume. I just tried this with btrfs-progs-0.20.rc1.20130501git7854c8b-4.fc20.x86_64 without -a option, but with a subvolume mounted and the command lists all subvolumes.
>
> OK now I'm seeing the behavior is sometimes wrong.
>
> [root@f19v ~]# btrfs subvolume create /mnt/cookies
> Create subvolume '/mnt/cookies'
> [root@f19v ~]# btrfs subvolume create /mnt/chips
> Create subvolume '/mnt/chips'
> [root@f19v ~]# btrfs subvolume create /mnt/nuts
> Create subvolume '/mnt/nuts'
> [root@f19v ~]# btrfs subvolume create /mnt/nuts/cashew
> Create subvolume '/mnt/nuts/cashew'
> [root@f19v ~]# btrfs subvolume create /mnt/nuts/cashew
> ERROR: '/mnt/nuts/cashew' exists
> [root@f19v ~]# btrfs subvolume create /mnt/nuts/cashew/small
> Create subvolume '/mnt/nuts/cashew/small'
> [root@f19v ~]# umount /mnt
> [root@f19v ~]# mount -o subvol=nuts/cashew /dev/sdb /mnt
> [root@f19v ~]# btrfs subvolume list /mnt
> ID 256 gen 5 top level 5 path cookies
> ID 258 gen 10 top level 5 path chips
> ID 259 gen 12 top level 5 path nuts
> ID 260 gen 13 top level 5 path nuts/cashew
> ID 261 gen 13 top level 260 path small
I get the following output:
cookies
chips
nuts
nuts/cashew
nuts/cashew/small
Why "small" occurs in your test box?
Thanks,
wang
>
>
> The last one should be /nuts/cashew/small. Or the one before it should be cashew instead of nuts/cashew.
>
>
> Chris Murphy
>
>
> --
> 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
prev parent reply other threads:[~2013-09-04 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 11:57 Btrfs prog Giuseppe Fierro
2013-09-04 13:32 ` Hugo Mills
2013-09-04 13:51 ` Giuseppe Fierro
2013-09-04 14:10 ` Chris Murphy
2013-09-04 14:26 ` Wang Shilong
2013-09-04 14:08 ` Chris Murphy
2013-09-04 14:37 ` Wang Shilong [this message]
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=5E29539F-9625-488E-AD90-A72A37DF20BD@gmail.com \
--to=wangshilong1991@gmail.com \
--cc=giuseppe@fierro.org \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).