Re: Recovering an Array with inconsistent Superblocks

[NeilBrown <neilb@suse.de>]

[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]

On Sun, 05 Jan 2014 13:25:29 -0500 Phil Turmel <philip@turmel.org> wrote:

> Hi Fabian,
> 
> I see good news to greet me this morning!
> 
> On 01/05/2014 05:45 AM, Fabian Knorr wrote:
> > $ cat /proc/mdstat 
> > Personalities : [raid6] [raid5] [raid4] 
> > md127 : active (auto-read-only) raid5 sde1[6] sdh1[2] sdi1[3] sdb1[4] sdg1[1] sdc1[5] sdf1[0]
> >       11721074688 blocks level 5, 1024k chunk, algorithm 2 [7/7] [UUUUUUU]
> >         resync=PENDING
> 
> Auto-read-only will switch to read-write as soon as you actually write
> anything to the array.  Which will also kick off the resync.

You can also "mdadm --readwrite /dev/md127" to allow resync to continue.


> Long term, consider creating a new array with metadata type 1.x so you
> can use a bitmap.  If you ever have an event like this, where one or
> more devices are disconnected then reconnected, it'll greatly shorten
> the recovery time.

While I would encourage the use for 1.x metadata, you don't strictly need it
for a bitmap.  0.90 metadata supports bitmaps too, though it is slightly less
flexibly in the granularity of the bitmap (not that you would probably
notice).

NeilBrown


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]