jdong
April 8th, 2005, 03:46 PM
Ok, I have a fs corruption bug that reproduces quite consistently. Here's how it goes:
1. Uncleanly unmount an XFS partition that contains GRUB. The Reset button is great for this purpose.
2. At next bootup, have GRUB write a change. This could be setup (hd0), or even "savedefault"
3. One of these happens:
a. An FSCK will turn up hundreds of errors, and files will be deleted.
b. Your superblock will be gone, GRUB refuses to recognize the drive; then, part (a)
c. You get lucky and escape unharmed.
This doesn't seem to happen at all with an ext3 /boot partition, and an XFS / partition. Lesson? Put "/boot" on a separate partition!
1. Uncleanly unmount an XFS partition that contains GRUB. The Reset button is great for this purpose.
2. At next bootup, have GRUB write a change. This could be setup (hd0), or even "savedefault"
3. One of these happens:
a. An FSCK will turn up hundreds of errors, and files will be deleted.
b. Your superblock will be gone, GRUB refuses to recognize the drive; then, part (a)
c. You get lucky and escape unharmed.
This doesn't seem to happen at all with an ext3 /boot partition, and an XFS / partition. Lesson? Put "/boot" on a separate partition!