Excerpts from John Wyzer's message of 2011-04-30 18:33:20 -0400: > Excerpts from Mitch Harder's message of Sun May 01 00:16:53 +0200 2011: > > > Hmm. > > > Tried it and it gives me about 500000 lines of > > > > > > FIBMAP: Invalid argument > > > > > > and then: > > > > > > large_file: 1 extent found > > > > > > Is that the way it is supposed to work? > > > Just asking because this was part of a vmware disk image. Both the virtual > > > machine and the rest of the host system are almost unusable once the VM > > > ist > > > started (even more unusable than without vmware :-D ) > > > > No. It sounds like the filefrag command is getting confused in the > > virtual environment. > > Misunderstanding :-) I tried filefrag _on_ a vmware disk image, not inside a > virtual machine. > The whole btrfs story here is on a real machine.
Older filefrag uses fibmap, which we don't support (we use fiemap instead). If you update your e2fsprogs you should get a newer filefrag. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
