On Fri, 2006-05-26 at 13:30 -0400, Mark Hahn wrote: > yes - the kernel traditionally doesn't, of its own accord, read files. > most stuff under /etc are inputs to user-level tools that run during > boot to instruct the kernel how to configure things. distros have, > in the past, had boot-time scripts that would run mdadm and thus > read your mdadm.conf (or the raid config files that predate mdadm...) > > so perhaps your observed change in behavior had to do with distro changes... I agree. There must have been a distro change over the past 3 years concerning the array build process. I seem to remember a great concern of mine to store my mdadm.conf off-site, just in case my rootfs drive died (which it did of course). I also never set the partition types to Linux raid either. So there's been a couple changes over the years, probably more. I will say this. My 2 1TB 14 drive servers have been extremely reliable for the past 3.5 years. Occasionally, I replace the power supply but that's about it. Just for your information, a drive will drop out of the array when the power supply starts to droop. When I have a drive failure, I pull the drive, externally run a bad block test and replace if necessary. If no errors, I replace the power supply and reinsert the old drive back into the array and rebuild. This has happened about 5 times for my 2 servers over the past 3 years. > > -- ------------------------------------------------------------ Dr. Craig Hollabaugh, craig@xxxxxxxxxxxxxx, 970 240 0509 Author of Embedded Linux: Hardware, Software and Interfacing www.embeddedlinuxinterfacing.com - 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
