http://bugzilla.kernel.org/show_bug.cgi?id=14354 --- Comment #108 from James Cloos <cloos@xxxxxxxxxxx> 2009-10-23 04:30:36 --- > I'd appreciate by the way getting reports from other people who have been > suffering file system corruption problems whether or not the patch in > attachment #23468 helps, and whether they are seeing any "File system is > read-only" followed by a kernel stack trace in their system logs. Thanks!! I got some corruption, but not ro changes. In an early rc nothing seemed wrong until, after a reboot, I saw enough corruption in a db that I had to dump, clean up several bogus records and restore it. (It was a busy but ephemeral db, so that wasn't too much of a problem. Today, however, running -rc5 the box simply rebooted without notice. and I got a number of log entries after the reboot. Most specified ext4_mb_generate_buddy and jbd complained that it spotted a dirty metadata buffer. There were also a couple of bad header/extents. I stut down enough to unmoount /var and ran e2fsck. That generated a *slew* of errors, mostly complaining about multiple files claiming the same blocks. A second e2fsck right after (with -f) showed no further errors. I now have about 70 megs of data in lost+found. The box is only partly up right now (I'm writing this over ssh); I'll be able to provide more details after a reboot.... -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- 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
