I very much doubt this was a problem with e2fsprogs, but rather with the RAID setup. If e2fsck was doing a full check after doing a journal replay, it's probably because the kernel had detected a filesystem consistency problem, and had set the "filesystem has an error" flag. The symptoms described sound very much like (a) hardware problems, or (b) a serious RAID configuration error (i.e., where part of the RAID is also getting used as a swap device, or something crazy like that). Given that all of your problems went away when you stopped using LVM, that makes it HIGHLY (as in 0.0000001% chance) that it is not an e2fsprogs problem, since e2fsprogs really doesn't care what the underlying disk device is. It (and the kernel filesystem code) only asks that the disk device be reliable, and what gets stored at a paticular block address stays stored there.
Part of the reason why no one probably looked at it is because it was coded as a e2fsprogs bug, and when I, as an unpaid volunteer, looked at the bug, it was obviously NOT a problem. I can say that I am using LVM for all of my ext3 filesystem, as do many Ubuntu users, so if there was a major systemic problem, it would have been reported by now. This makes it highly likely that either (a) there is something specifically unusual about your system or your configuration, which is why no one else is seeing it, or (b) there is a hardware problem, or (c) this was some kind of user error. -- Data corruption with ext3 in striped logical volume https://bugs.launchpad.net/bugs/100126 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
