From: NeilBrown <neilb@suse.de>
To: Christopher Hoover <ch@murgatroid.com>
Cc: Adam Goryachev <adam@websitemanagers.com.au>, linux-raid@vger.kernel.org
Subject: Re: unable to assemble (mostly?) clean array
Date: Mon, 9 Dec 2013 14:41:59 +1100 [thread overview]
Message-ID: <20131209144159.6d5121ca@notabene.brown> (raw)
In-Reply-To: <CACw0PsZ9=pL=D9fdQpzoFHCnm3DceEy_Erw0jjxpJgNjjTo9ew@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5133 bytes --]
On Sun, 8 Dec 2013 19:00:02 -0800 Christopher Hoover <ch@murgatroid.com>
wrote:
> OK, seems to be back to doing "something". See below.
>
> I'm a little concerned that it "promoted" sde1 rather than relying on
> the other three drives with the same event count.
Two of those three devices considered themselves to be 'spares' - so there is
no reason to believe there was useful data on them.
>
> Very much thank you for your help!
>
> -ch
>
> p.s. is there anyway to assemble a container from components in read
> only mode? I have a feeling i'm going to loved sde1 again before the
> recovery.
Not really, no.
NeilBrown
>
>
>
> ch@snaggle:~/src/mdadm$ sudo ./mdadm -Avf /dev/md0 /dev/sd[efdg]1
> mdadm: looking for devices for /dev/md0
> mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot 4.
> mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 1.
> mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot 2.
> mdadm: /dev/sdg1 is identified as a member of /dev/md0, slot 5.
> mdadm: forcing event count in /dev/sde1(1) from 286011 upto 286024
> mdadm: no uptodate device for slot 0 of /dev/md0
> mdadm: added /dev/sdf1 to /dev/md0 as 2
> mdadm: no uptodate device for slot 6 of /dev/md0
> mdadm: added /dev/sdd1 to /dev/md0 as 4
> mdadm: added /dev/sdg1 to /dev/md0 as 5
> mdadm: added /dev/sde1 to /dev/md0 as 1
> mdadm: /dev/md0 has been started with 2 drives (out of 4) and 2 spares.
>
> ch@snaggle:~/src/mdadm$ sudo mdadm -D /dev/md0
> /dev/md0:
> Version : 0.90
> Creation Time : Mon May 23 00:02:10 2011
> Raid Level : raid6
> Array Size : 2930271872 (2794.53 GiB 3000.60 GB)
> Used Dev Size : 1465135936 (1397.26 GiB 1500.30 GB)
> Raid Devices : 4
> Total Devices : 4
> Preferred Minor : 0
> Persistence : Superblock is persistent
>
> Update Time : Sun Dec 8 18:53:29 2013
> State : clean, degraded, recovering
> Active Devices : 2
> Working Devices : 4
> Failed Devices : 0
> Spare Devices : 2
>
> Layout : left-symmetric
> Chunk Size : 64K
>
> Rebuild Status : 0% complete
>
> UUID : 48af1ed4:8978e992:f8a6b934:875c877f (local to host snaggle)
> Events : 0.286025
>
> Number Major Minor RaidDevice State
> 4 8 97 0 spare rebuilding /dev/sdg1
> 1 8 65 1 active sync /dev/sde1
> 2 8 81 2 active sync /dev/sdf1
> 5 8 49 3 spare rebuilding /dev/sdd1
> ch@snaggle:~/src/mdadm$
>
>
> On Sun, Dec 8, 2013 at 5:33 PM, NeilBrown <neilb@suse.de> wrote:
> > On Sun, 8 Dec 2013 17:08:19 -0800 Christopher Hoover <ch@murgatroid.com>
> > wrote:
> >
> >> ch@snaggle:~$ sudo mdadm --assemble --verbose --force /dev/md0 /dev/sd[defg]1
> >> mdadm: looking for devices for /dev/md0
> >> mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot 4.
> >> mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 1.
> >> mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot 2.
> >> mdadm: /dev/sdg1 is identified as a member of /dev/md0, slot 5.
> >> mdadm: ignoring /dev/sde1 as it reports /dev/sdd1 as failed
> >> mdadm: ignoring /dev/sdf1 as it reports /dev/sdd1 as failed
> >> mdadm: no uptodate device for slot 0 of /dev/md0
> >> mdadm: no uptodate device for slot 1 of /dev/md0
> >> mdadm: no uptodate device for slot 2 of /dev/md0
> >> mdadm: no uptodate device for slot 3 of /dev/md0
> >> mdadm: added /dev/sdg1 to /dev/md0 as 5
> >> mdadm: added /dev/sdd1 to /dev/md0 as 4
> >> mdadm: /dev/md0 assembled from 0 drives and 2 spares - not enough to
> >> start the array.
> >> ch@snaggle:~$
> >
> > Thanks.
> >
> > I recognise this bug now. You are running mdadm-3.2.something - correct?
> > You need 3.3.
> > Just grab the latest:
> >
> > cd /tmp;git clone git://neil.brown.name/mdadm ; cd mdadm ; make ; ./mdadm -Avf /dev/md0 /dev/sd[defg]1
> >
> > NeilBrown
> >
> >
> >>
> >> On Sun, Dec 8, 2013 at 5:02 PM, NeilBrown <neilb@suse.de> wrote:
> >> > On Sun, 8 Dec 2013 16:32:22 -0800 Christopher Hoover <ch@murgatroid.com>
> >> > wrote:
> >> >
> >> >> yes, thanks, typo there. that was done hastily for the e-mail.
> >> >>
> >> >> i had tried the right thing previously and here it is again. still no luck:
> >> >>
> >> >>
> >> >> ch@snaggle:~$ sudo mdadm -E /dev/sd[defg]1 | egrep 'Events|^/dev/sd'
> >> >> /dev/sdd1:
> >> >> Events : 286024
> >> >> /dev/sde1:
> >> >> Events : 286011
> >> >> /dev/sdf1:
> >> >> Events : 286024
> >> >> /dev/sdg1:
> >> >> Events : 286024
> >> >> ch@snaggle:~$ sudo mdadm --assemble --force /dev/md0 /dev/sd[dfg]1
> >> >> mdadm: ignoring /dev/sdf1 as it reports /dev/sdd1 as failed
> >> >> mdadm: /dev/md0 assembled from 0 drives and 2 spares - not enough to
> >> >> start the array.
> >> >> ch@snaggle:~$
> >> >
> >> > Please try listing *all* of the devices, and add "-v" for extra output.
> >> >
> >> > NeilBrown
> >
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2013-12-09 3:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 23:32 unable to assemble (mostly?) clean array Christopher Hoover
2013-12-08 23:55 ` NeilBrown
2013-12-09 0:02 ` Adam Goryachev
2013-12-09 0:32 ` Christopher Hoover
2013-12-09 1:02 ` NeilBrown
2013-12-09 1:08 ` Christopher Hoover
2013-12-09 1:33 ` NeilBrown
2013-12-09 3:00 ` Christopher Hoover
2013-12-09 3:41 ` NeilBrown [this message]
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=20131209144159.6d5121ca@notabene.brown \
--to=neilb@suse.de \
--cc=adam@websitemanagers.com.au \
--cc=ch@murgatroid.com \
--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).