On Wednesday June 22, davidsen@xxxxxxx wrote: > > So is there no way to ask mdadm to take what's running and create a > config to make it happen again? Telling people to cread the man pages > for a utility they did not use by choice and create a config file which > could result in losing their data if it's wrong is a deterent to an > upgrade, I suspect. There is a complexity in that devices can change there names across reboot, and mdadm has no way to know a minimal set of possible new names. You could: echo DEVICES partitions > /etc/mdadm.conf mdadm -Ds | grep -v devices >> /etc/mdadm.conf and then mdadm -As should re-assemble everything properly at boot time. However this might not handle stacked devices (raid0 comprised for raid1s) very well (maybe an enhancement for the next mdadm?). A bad config file is unlikely to cause data loss. It might result it data not being visible until the problem is fixed. I'm working towards making auto-assembly more bullet-proof, but it is not trivial, and I would rather it not give the appearance of working correctly until it really does (in contrast to 'raidstart' which gives the appearance of working correctly until a drive fails. Then it fails too :-( ) NeilBrown - 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
