Andrey Borzenkov wrote: > There is long standing open bug report on Mandriva which is currently > beieved to have root cause in file system corruption. It shows itself > in RPM DB corruption (at least, there is no other known method to trigger > it). So far all reported cases happened on filesystem with 1K block size > and stopped when RPM DB was moved to FS with 4K block size. > > There are also similar RH reports as well. > > Here are references: > > https://qa.mandriva.com/show_bug.cgi?id=32547 > > This one is rather long. yep, unfortunately IIRC most of the bug is "me too's" and "how do I do the workaround" :) > Interesting bits are probably around > > https://qa.mandriva.com/show_bug.cgi?id=32547#c177 > https://qa.mandriva.com/show_bug.cgi?id=32547#c148 (many users reporting > dumpe2fs) > > https://bugzilla.redhat.com/show_bug.cgi?id=230362 > https://bugzilla.redhat.com/show_bug.cgi?id=375931 > https://bugzilla.redhat.com/show_bug.cgi?id=305301 > > The Mandriva bugzilla also mentions this mail from Stephen Tweedie > http://lkml.org/lkml/2007/9/18/232 I don't think this is related, in the end... there was some possiblity of corruption from that, but I think it's doubtful it'd hit 1k block filesystems more, and in any case, the corruption has been seen since then if I read it right. > which indicates some issues with 1K blocks, but according to last comment: > https://qa.mandriva.com/show_bug.cgi?id=32547#c300 > > it is still present in 2.6.27 (at least was present on -rc6) > > There was a kernel bug report http://bugzilla.kernel.org/show_bug.cgi?id=11564, > but in this case it was identified as hardware issue. My kingdom for a testcase... does anyone have simple steps to reproduce this? Or do they all start with "install mandriva on a 1k block size system?" :) -Eric -- 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
