On Tuesday April 24, leon.woestenberg@xxxxxxxxx wrote: > David, > > thanks for all the advice so far. > > On 4/24/07, David Greaves <david@xxxxxxxxxxxx> wrote: > > > > Essentially all --create does is create superblocks with the data you want (eg > > slot numbers). It does not touch other 'on disk data'. > > It is safe to run the *exact same* create command on a dormant array at any time > > after initial creation - the main side effect is a new UUID. > > (Neil - yell if I'm wrong). Close enough. The "active/clean" flag also gets changed. And for raid5, you want "--force" or it will make a degraded array with one spare which may not be what you want. > > > In first instance we were searching for ways to tell mdadm what we > know about the array (through mdadm.conf) but from all advice we got "mdadm.conf" doesn't really know anything about the shape of the array. It just describes how to discover and recognise component devices. The metadata on the device is authoritative, and if it is corrupt.... it is corrupt. > we have to take the 'usual' non-syncing-recreate approach. If "mdadm -f" doesn't work, then there is rarely any other option but re-creating the array. If you a reasonably careful the data will still be there (unless it was corrupted by whatever corrupted the metadata). 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
