also sprach Jim Paris <jim@jtan.com> [2007.04.02.2345 +0200]: > If those two disks were part of a RAID mirror and they were > written to individually, they could end up inconsistent, which may > have caused problems with the RAID later? Absolutely. Now we need to figure out how to get from here to an empty data partition. After the mount, both of sd[ab]1 would have to be recovered and usable, but out of sync. So when the raid was force-reassembled, md would sync the older from the newer. This should, in my book, result in a valid and full filesystem. I would assume that the fsck -b run then somehow screwed up the data. Maybe it's even a bug in fsck -b. And the other question of course is why the kernel decided it had any business doing recovery on an fs that was marked for ro mount. -- .''`. martin f. krafft <madduck@debian.org> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems
Attachment:
signature.asc
Description: Digital signature (GPG/PGP)