> On Tue, Mar 17, 2009 at 11:40:19AM +0200, Denis Karpov wrote: > > Hello, > > > > first off, sorry if you getting this email twice. > > No problem, I'm not exactly able to reproduce it myself, but Jan Kara > has just fixed some issues which could explain it: they happen under > memory pressure so I may not have triggered it if I didn't put it > under pressure. > > Jan's fixes are here: > > http://marc.info/?l=linux-ext4&m=123731584711382&w=2 > > It would be interesting to try them, and if they don't work maybe > he's also interested so I cc'ed him. > > > > I also tried to do ext3/ext4 fs smoketesting and used Adraian's > > script. I am consistently getting the same results - filesystem get's > > corrupted. > > I tested on quad Xeon, with patches posted in this thread. > > > > 1. tests with brd: > > - ext3fs on brd > > corruption (see attached ext3fs.brd.corruption.txt) > > - ext4fs on brd > > corruption (see attached ext4fs.brd.corruption.txt) > > > > In both cases I saw some complains from JBD/JBD2: > > JBD: Detected IO errors while flushing file data on Yes, my patches fix exactly this problem. So please try running with them. I'm not sure about that HTREE corruption you see during fsck. That seems to be a separate issue. > > 2. I enabled JBD debugging, re-run the tests. Console was > > flooded with messages and in the end I got a soft lockup. > > I cannot consistently reproduce this (see attached > > brd.ext3fs.softlock.txt). Yes, this usually produces far too many messages. The soft lockup was probably caused by the machine being too busy logging all the messages (log files are synced which adds much more to the load of the filesystem). I'd probably leave that aside for now and concentrate on the corruption problem. Honza -- Jan Kara <jack@xxxxxxx> SuSE CR Labs -- 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
