From: NeilBrown <neilb@suse.de>
To: Matthias.Blaesing@persona.de
Cc: linux-raid@vger.kernel.org
Subject: Re: Recovery of RAID1 fails (added disks stays as spare)
Date: Mon, 19 Aug 2013 18:04:28 +1000 [thread overview]
Message-ID: <20130819180428.20e94e9d@notabene.brown> (raw)
In-Reply-To: <FC7EE784B0E13748AA4FF80E6D4CD67212EB01@w8kmail2.konzern.intern>
[-- Attachment #1: Type: text/plain, Size: 2802 bytes --]
On Mon, 19 Aug 2013 07:48:20 +0000 <Matthias.Blaesing@persona.de> wrote:
> Hey,
> > Strange. I would definitely have expected one of those to start the
> > recovery.
> > Does anything appear in the kernel logs (e.g. output of 'dmesg')?
>
> Please see the attaches boot.msg - from my perspective it only confirms the results
> gained from the /proc/mdstat and mdadm output.
I guess I should have been more explicit.
It looks like you have just attached a log of what happened at boot.
I mean does anything appear in the dmesg output when you try to add the spare
device to the array.
>
> To give some more information - her the mdadm.conf:
>
> s15434194:~ # cat /etc/mdadm.conf
> CREATE owner=root group=disk mode=0660 auto=yes
>
> MAILADDR root
>
> DEVICE containers partitions
> ARRAY /dev/md1 level=raid1 num-devices=2 devices=/dev/sda1,/dev/sdb1
> ARRAY /dev/md3 level=raid1 num-devices=2 devices=/dev/sda3,/dev/sdb3
>
>
> Could it be that the problem lies in the order in the devices row? When I compare the working md1 and the non-working md3 array I see a difference in the mapping of devices to numbers:
No, the order is irrelevant.
The experiment below wouldn't change anything.
NeilBrown
>
> For md1:
>
> Number Major Minor RaidDevice State
> 0 8 1 0 active sync /dev/sda1
> 1 8 17 1 active sync /dev/sdb1
>
> For md3:
>
> Number Major Minor RaidDevice State
> 0 8 19 0 active sync /dev/sdb3
> 1 0 0 1 removed
>
> 2 8 3 - spare /dev/sda3
>
>
> Would this be worth a try (the disks need approx. 24 hours to reach the rebuild-state, so I'm reluctant to try without some hope) to do:
>
> 1. change the Array line in /etc/mdadm.conf for md3 to read (switching order):
> ARRAY /dev/md3 level=raid1 num-devices=2 devices=/dev/sdb3,/dev/sda3
> 2. Remove the spare sda3
> 3. Zero the superblock of sda3
> 4. Add sda3 again to the array
>
> ?
>
> Mit freundlichen Grüßen
>
> Matthias Bläsing
> Abt IT
> KompetenzCenter
>
> Tel.: 02351 950-344
> Fax.: 02351 950-222
> mailto: matthias.blaesing@persona.de
> www.persona.de
>
>
> persona service Verwaltungs AG & Co. KG
> Freisenbergstraße 31 • 58513 Lüdenscheid
> Tel.: (02351) 950-0 • Fax: (02351) 950-222
> Sitz Lüdenscheid • Registergericht Iserlohn, HRA Nr. 2930
>
> persönlich haftende Gesellschafterin: persona service AG
> Gartenstraße 93 • CH-4002 Basel
> Handelsregister Basel, Nr. CH-270.3.012.836-8
> diese vertreten durch den Verwaltungsrat:
> Georg Breucker (Präsident) und Dr. Sebastian Burckhardt
> www.persona.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-08-19 8:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 9:09 Recovery of RAID1 fails (added disks stays as spare) Matthias.Blaesing
2013-08-17 0:50 ` NeilBrown
2013-08-19 7:48 ` Matthias.Blaesing
2013-08-19 8:04 ` NeilBrown [this message]
2013-08-20 6:14 ` Matthias.Blaesing
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130819180428.20e94e9d@notabene.brown \
--to=neilb@suse.de \
--cc=Matthias.Blaesing@persona.de \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).