On Mar 6, 2014, at 7:13 PM, Martin T <m4rtntns@xxxxxxxxx> wrote: > Hi, > > while most of the Linux software-RAID related tutorials suggest to > have the mdadm.conf file up to date, then is it actually needed or > used any more? I mean all the data needed by kernel for creating the > RAID arrays should be stored in the superblocks, shouldn't it? Or in > which situation the mdadm.conf is needed? Good question. mdadm.conf is baked into the initramfs by dracut, along with mdadm, on Fedora systems. I haven't tried to willfully break it by deleting mdadm.conf and rebuilding the initramfs to see if it still works. I'm pretty sure it happens within the initramfs prior to the kernel even attempting to mount root. On systemd systems this could be better learned by passing systemd.log_level=debug systemd.log_target=console. The initramfs contains systemd, mdadm, mdadm.conf - and I'm pretty sure systemd activates that service, and then mdadm uses the mdadm.conf that's in the initramfs to assemble the array, and then systemd mounts it per the kernel command line which specifies root as an mduuid. Chris Murphy -- 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
