On Tue 01-06-10 11:03:37, Christoph Hellwig wrote: > On Mon, May 31, 2010 at 11:31:01PM +0200, Jan Kara wrote: > > Hmm, interesting because I've run test 113 again with a kernel somewhere > > between 2.6.34 and 2.6.35-rc1 and the filesystem is clean. So probably you > > are able to hit some kind of race I'm not able to. Could you check whether > > the corruption is caused by the O_DIRECT run or some other one? > > 113 is an AIO test, so it must be using O_DIRECT. Now I see that the third run of aio-stress failed so yes, it's using O_DIRECT. > > Also could you get "e2image -r" of the filesystem, bzip2 it and put it > > somewhere for download? > > I've jyst attached it as the compressed version is small enough (88k). I've looked at the image and for both corrupted inodes it looks as if we didn't write double-indirect block. The blocks which should be presumably referenced from it are properly allocated so it couldn't be just truncated or so. I've tried to reproduce the problem on another machine but failed... Is there anything special in your setup? Also are there any messages in the kernel log? Honza -- Jan Kara <jack@xxxxxxx> SUSE Labs, CR -- 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
