From: Li Zefan <lizf@cn.fujitsu.com>
To: "Ian! D. Allen" <idallen@idallen.ca>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs subvolume list fails to show all snapshots
Date: Fri, 21 Jan 2011 10:03:55 +0800 [thread overview]
Message-ID: <4D38E98B.8090901@cn.fujitsu.com> (raw)
In-Reply-To: <20110120230127.GB4161@idallen.ca>
07:01, Ian! D. Allen wrote:
> Still getting "btrfs subvolume list" errors with this source:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs-unstable.git
>
Just because the fix hasn't been merged into the git tree..
> I create ten snapshots, and after creating the tenth one, the sixth one
> disappears from "btrfs subvolume list":
next prev parent reply other threads:[~2011-01-21 2:03 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
2011-01-21 2:03 ` Li Zefan [this message]
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=4D38E98B.8090901@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=idallen@idallen.ca \
--cc=linux-btrfs@vger.kernel.org \
/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).