On Sunday February 23, norman.schmidt@ratnet.stw.uni-erlangen.de wrote: > > But if the last shutdown left the md devices dirty, they are resynced > during the next bootup while already in use. For normal ext2/ext3 data > partitions, this is no problem, but for swap and possibly ext-3 journals > this is deadly. Why do you think that resync is 'deadly' for 'swap and possibly ext-3 journals' ? There were problems like this in 2.2, but they are long gone, unless there is something else you are thinking of.. > > What I would like to have is an option in mdadm.conf (through which the > arrays are configured and started automatically) like "WAIT" which holds > up the boot process (i.e. usage of the not yet resynced devices) as long > as resync takes. And these devices should be resynced first, so that one > does not have to wait for the resync of a terabyte-big data array that > uses part of the same disks. There could be some value in atleast waiting until resync starts so that the order of arrays will match the order of resync. > > How can I determine the order of assembly anyway? From top to bottom in > the config file (at least for arrays that donīt share the same > disks)? Top to bottom. NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
