From: "Ian! D. Allen" <idallen@idallen.ca>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs subvolume list fails to show all snapshots
Date: Thu, 20 Jan 2011 18:01:27 -0500 [thread overview]
Message-ID: <20110120230127.GB4161@idallen.ca> (raw)
In-Reply-To: <4D05DD9A.2060206@cn.fujitsu.com>
Still getting "btrfs subvolume list" errors with this source:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs-unstable.git
I create ten snapshots, and after creating the tenth one, the sixth one
disappears from "btrfs subvolume list":
# btrfs subvolume list /mnt/sdb1
ID 256 top level 5 path snap000001
ID 257 top level 5 path snap000002
ID 258 top level 5 path snap000003
ID 259 top level 5 path snap000004
ID 260 top level 5 path snap000005
ID 262 top level 5 path snap000007
ID 263 top level 5 path snap000008
ID 264 top level 5 path snap000009
ID 265 top level 5 path snap000010
# ls -lt /mnt/sdb1
total 48
drwxr-xr-x 1 root root 42 Jan 20 17:55 ROOT/
dr-xr-xr-x 1 root root 208 Jan 20 17:55 ./
dr-xr-xr-x 1 root root 28 Jan 20 17:55 snap000001/
dr-xr-xr-x 1 root root 28 Jan 20 17:55 snap000002/
dr-xr-xr-x 1 root root 28 Jan 20 17:55 snap000003/
dr-xr-xr-x 1 root root 28 Jan 20 17:55 snap000004/
dr-xr-xr-x 1 root root 28 Jan 20 17:55 snap000005/
dr-xr-xr-x 1 root root 28 Jan 20 17:55 snap000006/
dr-xr-xr-x 1 root root 28 Jan 20 17:55 snap000007/
dr-xr-xr-x 1 root root 28 Jan 20 17:55 snap000008/
dr-xr-xr-x 1 root root 28 Jan 20 17:55 snap000009/
dr-xr-xr-x 1 root root 28 Jan 20 17:55 snap000010/
drwxr-xr-x 4 root root 4096 Jan 20 15:30 ../
On Mon, Dec 13, 2010 at 04:47:22PM +0800, Li Zefan wrote:
> > After creating snapshot 10 from snapshot 9, snapshot 6 vanished from
> > the output of "btrfs subvolume list /dev/sdf1":
> >
> > # btrfs subv list /mnt/sdf1
> > ID 256 top level 5 path snap000001
> > ID 257 top level 5 path snap000002
> > ID 258 top level 5 path snap000003
> > ID 259 top level 5 path snap000004
> > ID 260 top level 5 path snap000005
> > ID 262 top level 5 path snap000007
> > ID 263 top level 5 path snap000008
> > ID 264 top level 5 path snap000009
> > ID 265 top level 5 path snap000010
> >
> ...
> > Surely something is wrong here?
> >
>
> Right, there's something wrong and I've figured it out.
> Will send out a fix soon.
> Thanks for the report!
--
| Ian! D. Allen - idallen@idallen.ca - Ottawa, Ontario, Canada
| Home Page: http://idallen.com/ Contact Improv: http://contactimprov.ca/
| College professor (Free/Libre GNU+Linux) at: http://teaching.idallen.com/
| Defend digital freedom: http://eff.org/ and have fun: http://fools.ca/
next prev parent reply other threads:[~2011-01-20 23:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 3:43 btrfs subvolume snapshot hung in btrfs_commit_transaction Ian! D. Allen
2010-12-12 8:14 ` Ian! D. Allen
2010-12-12 9:45 ` btrfs subvolume list fails to show all snapshots Ian! D. Allen
2010-12-13 8:47 ` Li Zefan
2011-01-20 23:01 ` Ian! D. Allen [this message]
2011-01-21 2:03 ` Li Zefan
2010-12-14 2:23 ` btrfs subvolume snapshot hung in btrfs_commit_transaction Ian! D. Allen
2010-12-17 1:47 ` Chris Mason
2010-12-17 4:45 ` Ian! D. Allen
2010-12-17 14:52 ` 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=20110120230127.GB4161@idallen.ca \
--to=idallen@idallen.ca \
--cc=linux-btrfs@vger.kernel.org \
--cc=lizf@cn.fujitsu.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).