From: Stephane Chazelas <stephane_chazelas@yahoo.fr>
To: Hugo Mills <hugo@carfax.org.uk>,
Andreas Philipp <philipp.andreas@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: strange btrfs sub list output
Date: Fri, 27 May 2011 10:30:29 +0100 [thread overview]
Message-ID: <chaz20110527093029.GA30613@seebyte.com> (raw)
In-Reply-To: <20110527091224.GA15627@carfax.org.uk>
2011-05-27 10:12:24 +0100, Hugo Mills:
[skipped useful clarification]
>
> That's all rather dense, and probably too much information. Hope
> it's helpful, though.
[...]
It is, thanks.
How would one end up in a situation where the output of "btrfs
sub list ." has:
ID 287 top level 285 path data
How could a "subvolume 285" become a "top level"?
How does one get a subvolume with a top-level other than "5"?
--
Stephane
next prev parent reply other threads:[~2011-05-27 9:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 21:22 strange btrfs sub list output Stephane Chazelas
2011-05-27 8:01 ` Stephane Chazelas
2011-05-27 8:21 ` Andreas Philipp
2011-05-27 8:47 ` Stephane Chazelas
2011-05-27 9:01 ` Stephane Chazelas
2011-05-27 9:12 ` Hugo Mills
2011-05-27 9:24 ` Andreas Philipp
2011-05-27 9:30 ` Stephane Chazelas [this message]
2011-05-27 9:45 ` Hugo Mills
2011-05-27 10:06 ` Andreas Philipp
2011-05-27 10:29 ` Hugo Mills
2011-05-27 11:30 ` Stephane Chazelas
2011-05-27 11:38 ` Hugo Mills
2011-05-27 11:49 ` Andreas Philipp
2011-05-31 10:00 ` Stephane Chazelas
2011-05-31 17:40 ` C Anthony Risinger
2011-05-31 18:50 ` Andreas Philipp
2011-05-31 19:32 ` C Anthony Risinger
2011-06-02 6:23 ` C Anthony Risinger
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=chaz20110527093029.GA30613@seebyte.com \
--to=stephane_chazelas@yahoo.fr \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=philipp.andreas@gmail.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).