From: Michael Evans <mjevans1983@gmail.com>
To: Ken D'Ambrosio <ken@jots.org>
Cc: Neil Brown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: RAID MIA. Again. (Kinda.)
Date: Fri, 5 Mar 2010 12:05:32 -0800 [thread overview]
Message-ID: <4877c76c1003051205i23998a72xc9df3174c1e7fd17@mail.gmail.com> (raw)
In-Reply-To: <a65d84c03d315f1aea40641238f25625.squirrel@webmail.jots.org>
On Fri, Mar 5, 2010 at 7:24 AM, Ken D'Ambrosio <ken@jots.org> wrote:
> On Thu, March 4, 2010 8:30 pm, Neil Brown wrote:
>> Try this:
>>
>>
>> cat /etc/fstab cat /etc/mdadm.conf mdadm -Esvv mdadm -Asv blkid -p /dev/md*
>>
>> And include all the output.
>
> See attached. Note that fstab is essentially irrelevant; I'd mounted by
> hand, and was going to add the entry after I got the server back in the
> server room.
>
>> (sorry if I seem grumpy, but I'm a bit tired which makes it harder to
>> appear polite).
>
> Know what you mean; got four hours', myself, due to a virtualization
> migration.
>
> For the record, I've got my backup tapes ordered (again) -- if you can
> tell me what I did wrong, that would be almost as satisfying as getting
> the data back.
>
> Thanks,
>
> -Ken
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
Here's a stab at it. I've never tried to do it like this and haven't
glanced at the code so I can't be sure, but this seems to be the most
likely suspect:
#ARRAY /dev/md0 level=raid5 num-devices=4 devices=sda2,sdb2,sdd2,sdc2
Your commented out version seems to specify this mapping
0,sda2
1,sdb2
2,sdd2
3,sdc2
However the array is detected like this by uuid alone (I re-ordered
the entries so they're easier to read):
mdadm: /dev/sdb2 is identified as a member of /dev/md0, slot 0.
mdadm: /dev/sdc2 is identified as a member of /dev/md0, slot 1.
mdadm: /dev/sda2 is identified as a member of /dev/md0, slot 2.
mdadm: /dev/sdd2 is identified as a member of /dev/md0, slot 3.
mdadm: added /dev/sdb2 to /dev/md0 as 0
mdadm: added /dev/sdc2 to /dev/md0 as 1
mdadm: added /dev/sda2 to /dev/md0 as 2
mdadm: added /dev/sdd2 to /dev/md0 as 3
mdadm: /dev/md0 has been started with 4 drives.
This corresponds to:
0,sdb2
1,sdc2
2,sda2
3,sdd2
Note how the drives are out of order? Thus the reason for only using
UUID and NOT explicitly specifying an ordering?
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-03-05 20:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 16:12 RAID MIA. Again. (Kinda.) Ken D'Ambrosio
2010-03-04 20:50 ` Neil Brown
2010-03-04 22:00 ` Ken D'Ambrosio
[not found] ` <4877c76c1003041421s42717938he6567434b74ec125@mail.gmail.com>
2010-03-04 22:24 ` Michael Evans
2010-03-04 23:41 ` Ken D'Ambrosio
2010-03-05 1:22 ` Michael Evans
2010-03-05 1:30 ` Neil Brown
2010-03-05 15:24 ` Ken D'Ambrosio
2010-03-05 20:05 ` Michael Evans [this message]
2010-03-05 20:38 ` Neil Brown
2010-03-06 3:18 ` Michael Evans
2010-03-05 20:37 ` Neil Brown
2010-03-09 14:43 ` Ken D'Ambrosio
2010-03-09 16:29 ` John Robinson
2010-03-09 19:49 ` Neil Brown
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=4877c76c1003051205i23998a72xc9df3174c1e7fd17@mail.gmail.com \
--to=mjevans1983@gmail.com \
--cc=ken@jots.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).