Bug#417407: debian-installer: d-i destroyed existing raid device
On Tue, Apr 03, 2007 at 10:39:26AM +0200, martin f krafft wrote:
> also sprach martin f krafft <firstname.lastname@example.org> [2007.04.03.1028 +0200]:
> > After the mount, both of sd[ab]1 would have to be recovered and
> > usable, but out of sync.
> Actually, as Sesse claims, it's entirely likely that md didn't think
> the partitions were out of sync. That would explain some pretty bad
> data screwage. But an empty filesystem?
Checkpoint of the IRC discussion:
- The submitter says that after reboot, the RAID was reported as out of
- The logs show that the ext3 filesystem was automatically mounted rw for
journal recovery by the kernel driver.
- There is no evidence in the logs that the RAID was ever assembled within
d-i, so it shouldn't be the case that the RAID superblocks were out of
sync as a result of d-i itself.
- This leaves two possible reasons for the out-of-sync state of the RAID:
either mounting the individual partitions as ext3 filesystems somehow
overwrote the RAID superblock just the right way (unlikely since it would
require the ext3 driver to write past the end of the declared filesystem),
or the RAID superblocks were out of sync /before/ booting d-i. The latter
is consistent with the fact that the ext3 driver had to do a journal
recovery, suggesting that both the ext3 fs and the RAID were not cleanly
- If mounting as ext3 overwrote the RAID superblock, that seems to be a
kernel bug, and we have no good explanation for how that would happen.
- If the RAID was unclean before booting d-i, all bets are off as to the
state of the filesystem at the beginning of this journal recovery, and it
may be difficult to ever reproduce this bug.
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.