From: Eric Sandeen <sandeen@redhat.com>
To: Tao Ma <tao.ma@oracle.com>
Cc: linux-ext4@vger.kernel.org, Theodore Tso <tytso@mit.edu>,
linux-kernel@vger.kernel.org
Subject: Re: fiemap is broken for sparse file in ext4?
Date: Fri, 11 Jun 2010 08:43:48 -0500 [thread overview]
Message-ID: <4C123D94.7060003@redhat.com> (raw)
In-Reply-To: <4C11C41C.9070000@oracle.com>
Tao Ma wrote:
> Hi Eric,
> Thanks for the quick response.
>
> On 06/11/2010 12:08 PM, Eric Sandeen wrote:
...
>> What are you using to call fiemap? Here it seems to be working:
> I just wrote a simple test program by calling ioctl. It is attached.
> btw, you need to call it immediately after dd so that we have a chance
> that ext4 don't have time to allocate extents. ;)
>>
>> # dd if=/dev/zero of=testfile1 bs=1M count=1 seek=1;
>>
>> # filefrag -v testfile1
>> Filesystem type is: ef53
>> Filesystem cylinder groups is approximately 119
>> File size of testfile1 is 2097152 (512 blocks, blocksize 4096)
>> ext logical physical expected length flags
>> 0 256 151946 1 merged
>> 1 257 151951 151946 2 merged
>> 2 259 152434 151952 253 merged,eof
>> testfile1: 4 extents found
> I guess maybe filefrag use the diffrent ioctl flag, maybe
> FIEMAP_FLAG_SYNC to let ext4 sync first.
My tester isn't calling sync or using the sync flag, AFAIK.
I'll take a look at yours.
Thanks,
-Eric
> Regards,
> Tao
>
next prev parent reply other threads:[~2010-06-11 13:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 2:15 fiemap is broken for sparse file in ext4? Tao Ma
2010-06-11 4:08 ` Eric Sandeen
2010-06-11 5:05 ` Tao Ma
2010-06-11 13:43 ` Eric Sandeen [this message]
2010-06-11 15:46 ` Eric Sandeen
2010-06-11 16:46 ` Greg Freemyer
2010-06-11 16:56 ` Eric Sandeen
2010-06-11 23:46 ` Tao Ma
2010-06-11 23:55 ` Eric Sandeen
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=4C123D94.7060003@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tao.ma@oracle.com \
--cc=tytso@mit.edu \
/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).