Description of problem: I found out that on Fedora 17, filefrag -v returns wrong extent count. In fact, the utility behaves similar as described in https://bugzilla.redhat.com/show_bug.cgi?id=653234 but the behavior is opposite now. Version-Release number of selected component (if applicable): e2fsprogs-1.42.3-2.fc17 How reproducible: Always Steps to Reproduce: 1. touch foo 2. filefrag foo 3. filefrag -v foo Actual results: 0 [mkyral@localhost ~ ]$ filefrag foo foo: 1 extent found ^^^^^ 0 [mkyral@localhost ~ ]$ filefrag -v foo Filesystem type is: ef53 File size of foo is 0 (0 blocks, blocksize 4096) foo: 0 extents found ^^^^^ Expected results: 0 [mkyral@localhost ~ ]$ filefrag foo foo: 1 extent found ^^^^^ 0 [mkyral@localhost ~ ]$ filefrag -v foo Filesystem type is: ef53 File size of foo is 0 (0 blocks, blocksize 4096) foo: 1 extent found Additional info:
Well, actually, if you simply "touch foo" then it has 0 extents. You should get 0 in both cases... There was a patch on the list last April, "[PATCH] E2fsprogs/filefrag: fix filefrag regression" which addressed this but never got merged. I'll review it & ping Ted. Thanks, -Eric
commit 036fda6d487737eac9be086d999b7480a81d37ea Author: Liu Bo <liubo2009.com> Date: Sat Jul 28 17:29:13 2012 -0400 filefrag: fix report of number of extents fixed this. Present in v1.42.5; I don't really think it needs an update pushed to F17. If you disagree, please reopen and I can do so.