Just to make data restoring a bit safer - one can use device mappers's snapshot feature as it can snapshot _any_ block device, you can create snapshots of say /dev/sda1 & /dev/sdb1 , then do your raid experiments on that snapshotted devices. More info http://www.mjmwired.net/kernel/Documentation/device-mapper/snapshot.txt https://www.redhat.com/archives/dm-devel/2004-July/msg00071.html 2011/7/23 Mikael Abrahamsson <swmike@xxxxxxxxx>: > On Sat, 23 Jul 2011, Vasco Névoa wrote: > >> I initially used "mdadm --create --assume-clean ..." on a level1 array of >> 2 disks that came from another machine. I didn't know any other way of >> starting an array in this situation. While this is an acceptable practice in >> some cases, it is better to use "--assemble" and pass the necessary info >> (like uuid). > > In case someone finds this from the archives: > > mdadm --create --assume-clean is a LAST RESORT. It's to be used when > everything else fails. I've seen so many start doing this way too early in > the process and who then subsequently lost their data because of superblock > version and mdadm changes over time (especially when they forgot > --assume-clean and got the layout wrong). > > -- > Mikael Abrahamsson email: swmike@xxxxxxxxx -- Best regards, [COOLCOLD-RIPN] -- 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
