http://bugzilla.kernel.org/show_bug.cgi?id=12885 ------- Comment #11 from andy-kernelbugzilla@xxxxxxxxxxxxxxx 2009-03-18 11:14 ------- (In reply to comment #8) > One interesting thing you could try, if you can go to 2.6.29-rc8, is you could > try mounting your ext3 filesystem using ext4, and see if the problem goes away > or not. If the problem sticks around, then that's actually very interesting, > since so much has changed between ext3 and ext4. If it goes away, that could > be a solution for you, but it also could be that it's just harder to reproduce > on ext4. Might we not loose the bug that way, as in it'd be gone for ever? Can I do that read-only? > This smells like a bug in jbd layer, or perhaps some assumption which is > getting violated by LUKS; since if it was as simple as just doing a backup of a > tree while another process was copying data into it, ext3 is such a commonly > used file system that I would have thought such a problem would have been > discovered by now. So if we have something like this which can be easily > reproduced, I really want to try to get it chased down. It's as easy as *reading* the afaics. I'll test this some more. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. -- 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
