From: Artem Bityutskiy <dedekind1@gmail.com>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-btrfs@vger.kernel.org, linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: imperfect FIEMAP results on btrfs
Date: Fri, 03 May 2013 08:57:11 +0300 [thread overview]
Message-ID: <1367560631.23415.2.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20130502233103.GA15549@dastard>
On Fri, 2013-05-03 at 09:31 +1000, Dave Chinner wrote:
> IOWs, you simply can't assume that a specific test will give you the
> same block layout across filesystems and different filesystem
> configurations. Welcome to the world of "can't assume anything about
> block layout" pain xfstests has been dealing with for years ;)
This is what I also assumed, but wanted to get some feed-back from the
community. Thanks a lot for the answer!
--
Best Regards,
Artem Bityutskiy
prev parent reply other threads:[~2013-05-03 5:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 16:00 imperfect FIEMAP results on btrfs Artem Bityutskiy
2013-05-02 16:08 ` Artem Bityutskiy
2013-05-02 23:31 ` Dave Chinner
2013-05-03 5:57 ` Artem Bityutskiy [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=1367560631.23415.2.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=david@fromorbit.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@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).