From: Chris Samuel <chris@csamuel.org>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Andreas Philipp <philipp.andreas@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: strange filefrag output on btrfs
Date: Tue, 14 Jun 2011 17:52:26 +1000 [thread overview]
Message-ID: <4DF7133A.2010001@csamuel.org> (raw)
In-Reply-To: <4DF6CD61.6050102@cn.fujitsu.com>
On 14/06/11 12:54, Li Zefan wrote:
> There are two ways to calc the extent number, depending
> on whether verbose option is turned on or not.
To me that's very counter intuitive!
Maybe another way to do that is to name those two values
differently and in verbose mode report them both so people
can see that there is a match ?
cheers,
Chris
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
prev parent reply other threads:[~2011-06-14 7:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 15:39 strange filefrag output on btrfs Andreas Philipp
2011-06-13 11:50 ` David Sterba
2011-06-13 15:16 ` Andreas Philipp
2011-06-14 2:54 ` Li Zefan
2011-06-14 7:11 ` Andreas Philipp
2011-06-14 7:52 ` Chris Samuel [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=4DF7133A.2010001@csamuel.org \
--to=chris@csamuel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--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).