linux-kernel - Re: 2.6.29 - raid10 issue - spares do not get synched automatically

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <e9c3a7c20903281743o2b9f7aa5yc60a330fee6de2ba@mail.gmail.com>
Date:	Sat, 28 Mar 2009 17:43:18 -0700
From:	Dan Williams <dan.j.williams@...il.com>
To:	Patrick Ringl <patrick_@...enet.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.29 - raid10 issue - spares do not get synched automatically

On Sat, Mar 28, 2009 at 4:55 AM, Patrick Ringl <patrick_@...enet.de> wrote:
> Hello,
>
> I am using 2.6.29 on a debian lenny. Anyway, I am having problems with a
> raid10 sandbox setup consisting of 4 loopback devices. To make a long story
> short:
>
> I created a raid10 array with all these 4 devices (loop0-loop3)
> then I set two devices faulty, removed them .. checked if I can still write
> to the array (which I could, so I/O errors, nothing in dmesg):
>
> BUT - here it comes: once I am trying to (re)add them (I zero'ed the
> superblock before) they're only getting added as spares and the array will
> not sync.
>
> Here's the logfile with mdadm -D /dev/md0 in between so one can see what is
> going on:
>
> http://paste.debian.net/31758/
>
>
> Any ideas?

You failed the whole array.  With 4 devices in the default layout the
array looks like stripe(mirror(slot0, slot1), mirror(slot2, slot3)).
In your case mdadm -D shows that you have the loop devices in the
following slots stripe(mirror(loop2, loop0), mirror(loop1, 3)).  A
raid10 is failed once all devices in a mirror set are failed, and a
failed array can't be rebuilt.

Regards,
Dan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/