On Sat, Jan 25, 2014 at 08:22:56PM +0000, Ian Nartowicz wrote: > Ian Nartowicz <claws <at> nartowicz.co.uk> writes: > > > > > I have been trying to test the inline_data feature of EXT4. I am using > > kernel 3.9.5 and have compiled e2fsprogs from the pu branch. I am able to > > set the feature and apparently to use the filesystem, but I get a lot of > > warnings from the kernel and fsck reports several errors and then crashes. > > > I wonder if I might have compiled against the wrong (clib?) headers? Are > you aware of any version dependencies in the pu branch tools? I doubt it; this looks like a straightforward memory bug of some kind (i.e., use after free, etc.) Could you try running e2fsck under valgrind? And could you also confirm the git commit ID of the e2fsprogs pu branch that you used to compile it? A compressed raw e2image file would be useful as well, but one problem with inline data is that a raw e2image file will have some amount of file data (for the small files that are using inline data) in the e2image file. We should probably look at teaching e2image to can zero out the contents of inline data files.... Many thanks, - Ted -- 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
