Theodore Tso wrote:
> On Sun, Aug 10, 2008 at 12:54:00PM -0500, Eric Sandeen wrote:
>> Hm, and I tried writing out 10 files in order as a simple test but
>> umount/remount brought me back many 0-byte files, I need to update my
>> patchset I guess. :)
>>
>
> One of the questions in my mind is whether this is a regression
> triggered by the some of our most recent patches.... since I only
> have 2.2% files reported a fragmented by e2fsck, and if this problem
> had always been there, I would have expected a much higher
> fragmentation number. So if you have some older kernels, you might
> want to see if you can replicate the problem. I've since found that
> just doing a copy via "(tar -cf - -C / usr/include ) | tar -C /mnt -xf -)"
> is sufficient to see the problem. Just add a "sync; sleep 5" before
> the umount. :-)
It may be; I tried this and then a quick filefrag run:
# filefrag usr/include/*.h | grep -v extents | awk -F : '{print $2}' |
sort | uniq -c
146 1 extent found
so everything came out contiguous.
This was with 2.6.27-0.186.rc0.git15.fc10.x86_64
-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
