> > Per the thread, Leslie is not seeing anything in the logs. > > That was a long thread. Heh... yeah, at the first look, it looks like > more of VM / FS interaction problem than low level driver problem. Either that, or a bug in Reiserfs, would be my guess. > Using blktrace/blkparse to track IO insertion, issue and completion > latencies would help to whether the problem is above the block layer > or below it. I'll look into this, too. I may need some guidance. > If you can bear with slower operation, keeping issuing sync repeatedly > (ie. something like while true; do sync; sleep 1; done) and see how > the behavior changes might shed some light on what's going on too. I wouldn't expect it to have any diagnostic value, really. The sync command locks up just like every other disk I/O when the event occurs. > Also, disabling journal and seeing how the behavior changes could be > revealing too. Well, first of all, I would not expect this to have much effect (one never knows, of course), because the event can transpire when there are no writes at all going on and no dirty blocks, although once again one never knows. Secondly, how does one disable the journal in Reiserfs? -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
