Thanks, Neil. I experimented with --force switch, and I saw that when using this switch it is possible to start the array, even though I am sure that the data will be corrupted. Such as selecting stale drives (which have been replaced previously etc.) Can I have some indication that it is "relatively safe" to start the array with --force? For example, in the case of "dirty degraded", perhaps it might be relatively safe. What should I look at? The output of --examine? Or something else? Thanks, Alex. On Wed, Oct 12, 2011 at 5:45 AM, NeilBrown <neilb@xxxxxxx> wrote: > On Tue, 11 Oct 2011 15:11:47 +0200 Alexander Lyakas <alex.bolshoy@xxxxxxxxx> > wrote: > >> Hello Neil, >> can you please confirm for me something? >> In case the array is FAILED (when your enough() function returns 0) - >> for example, after simultaneous failure of all drives - then the only >> option to try to recover such array is to do: >> mdadm --stop >> and then attempt >> mdadm --assemble >> >> correct? > > Yes, though you will probably want a --force as well. > >> >> I did not see any other option to recover such array Incremental >> assemble doesn't work in that case, it simply adds back the drives as >> spares. > > In recent version of mdadm it shouldn't add them as spare. It should say > that it cannot add it and give up. > > 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
