From: "NeilBrown" <neilb@suse.de>
To: David Rea <dave@daverea.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID-5 spare drive: Can't make spare persist across reboot
Date: Sun, 31 May 2009 08:44:07 +1000 (EST) [thread overview]
Message-ID: <f9fa44a3d9376b5e2b4c624bd36fab89.squirrel@neil.brown.name> (raw)
In-Reply-To: <984c80610905301526h6a71b79cyd1cb66c992db355a@mail.gmail.com>
On Sun, May 31, 2009 8:26 am, David Rea wrote:
> On Sat, May 30, 2009 at 5:53 PM, Neil Brown <neilb@suse.de> wrote:
>
>>> However, after a reboot, I'm back to 3 active and 0 spare drives.
>>> [snip]
>>
>> This should "just work". There might be some hints in
>> /var/log/messages if you'd like to post that.
>
> Here is the output of `cat /var/log/messages | grep raid`:
> http://pastebin.ca/1441575
That isn't very useful. Getting the whole /var/log/messasges
would be best - then I can see what isn't there as well as what is.
maybe
grep -C 10 -E '(md|raid)' /var/log/messages
might be enough.
>
> It seems that raid5 only sees the sd[acd] as active drives, but
> doesn't pick up the spare.
>
>>> -- Is there any way to instantiate a superblock on /dev/sdb1 so that
>>> it can be associated with this array's UUID?
>>
>> You have already done that. Use
>> mdadm --examine /dev/sdb
>> to confirm.
>
> This successfully identifies /dev/sdb1 as a spare:
> http://pastebin.ca/1441576
> However running `mdadm --examine /dev/sda` for example does not:
> http://pastebin.ca/1441578
That would be because the array was assembled without /dev/sdb1
so even if sda knew about it before, it will have been told to forget.
Is there a reason why you are using whole drives (sda, sdc, sdd) for
some devices, and just a partition (sdb1) for others?
> And running `mdadm --detail /dev/md0` also says no spares:
> http://pastebin.ca/1441579
>
> (let me know if you'd rather I paste these inline, for archival
> purposes or what have you)
Inline is generally easier to work with, unless things are huge.
NeilBrown
>
>>> -- I have the ARRAY line (in mdadm.conf) specified by UUID; could this
>>> be causing the spare to be excluded, since it (presumably) does not
>>> have a superblock?
>>
>> No. And it does have a superblock.
>
> Gotcha, I stand corrected! I guess at this point I just need to figure
> out how to get the spare to recognize on bootup, since it's already
> got the same UUID and is listed in mdadm.conf:
> http://pastebin.ca/1441588
>
> Thanks again for your help,
> Dave
>
--
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:[~2009-05-30 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-30 18:37 RAID-5 spare drive: Can't make spare persist across reboot David Rea
2009-05-30 21:53 ` Neil Brown
2009-05-30 22:26 ` David Rea
2009-05-30 22:44 ` NeilBrown [this message]
2009-05-31 0:31 ` David Rea
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=f9fa44a3d9376b5e2b4c624bd36fab89.squirrel@neil.brown.name \
--to=neilb@suse.de \
--cc=dave@daverea.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