Moshe Yudkowsky wrote: > Michael Tokarev wrote: > >> Speaking of repairs. As I already mentioned, I always use small >> (256M..1G) raid1 array for my root partition, including /boot, >> /bin, /etc, /sbin, /lib and so on (/usr, /home, /var are on >> their own filesystems). And I had the following scenarios >> happened already: > > But that's *exactly* what I have -- well, 5GB -- and which failed. I've > modified /etc/fstab system to use data=journal (even on root, which I > thought wasn't supposed to work without a grub option!) and I can > power-cycle the system and bring it up reliably afterwards. > > So I'm a little suspicious of this theory that /etc and others can be on > the same partition as /boot in a non-ext3 file system. If even your separate /boot failed (which should NEVER fail), what to say about the rest? I mean, if you'll save your /boot, what help it will be for you, if your root fs is damaged? That's why I said /boot is mostly irrelevant. Well. You can have some recovery stuff in your initrd/initramfs - that's for sure (and for that to work, you can make your /boot more reliable by creating a separate filesystem for it). But if to go this route, it's better to boot off some recovery CD instead of trying recovery from very limited toolset available in your initramfs. /mjt - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
