From: David Watson <David.Watson@team17.com>
To: linux-raid@vger.kernel.org
Subject: Re: Raid 1 array degrades on reboot [resolved]
Date: Fri, 18 Jun 2010 17:14:23 +0100 [thread overview]
Message-ID: <4C1B9B5F.1050007@team17.com> (raw)
In-Reply-To: <20100618073440.373d8aa6@notabene.brown>
Neil Brown wrote:
> On Thu, 17 Jun 2010 11:15:11 +0100
> David Watson <David.Watson@team17.com> wrote:
>
>> Hello,
>>
>> Recently I upgraded to 2Tb disks on one of my servers, I built a new
>> degraded raid1 array:
>> mdadm --create /dev/md7 -level 1 --raid-devices=2 missing /dev/sdd1
>>
>> added its entry to /etc/mdadm/mdadm.conf then I rebooted to add the
>> second disk and added it to the array:
>> mdadm --manage /dev/md7 --add /dev/sdb1
>>
>> I updated /etc/mdadm/mdadm.conf, although I noticed no difference in the
>> output of:
>> mdadm --detail --scan
>>
>>
>> I use a monolithic kernel so there is no ramdisk to regenerate. This is
>> my first 1.00 array, and the existing 0.9 arrays have never shown this
>> issue. I have attempted the same process on a test server with no
>> issues, and I can't really think of what to look at next.
>>
>> apologies for the long post.
>>
>
> Long posts are good....
> However I cannot see in your long post what the actual problem is.
> You have given no evidence that anything degrades on boot.
> No kernel logs, no "/proc/mdstat immediately after boot"...
>
> More info please.
>
> NeilBrown
> --
Trivial error:
/etc/mdadm/mdadm.conf
DEVICE /dev/sda* /deb/sdb* /dev/sdc* /dev/sdd*
Typo: /deb/sdb* should have been /dev/sdb*
Apologies, its taken a week for me to spot this.
Array now remains synchronised through a reboot.
Thanks
David Watson
prev parent reply other threads:[~2010-06-18 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 10:15 Raid 1 array degrades on reboot David Watson
2010-06-17 21:34 ` Neil Brown
2010-06-18 16:14 ` David Watson [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=4C1B9B5F.1050007@team17.com \
--to=david.watson@team17.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