From: Paul Clements <Paul.Clements@SteelEye.com>
To: linux@horizon.com
Cc: linux-raid@vger.kernel.org
Subject: Re: Minor RAID-1 oddity... any way to fix?
Date: Thu, 04 Sep 2003 16:43:03 -0400 [thread overview]
Message-ID: <3F57A3D7.D3E77710@SteelEye.com> (raw)
In-Reply-To: 20030904203719.16703.qmail@science.horizon.com
linux@horizon.com wrote:
> md3 : active raid1 hde3[2] hdi3[1]
> 58612096 blocks [2/1] [_U]
> [====>................] recovery = 21.1% (12401216/58612096) finish=36.6min speed=20987K/sec
[snip]
> Notice that in md1 and md7, it took its usual drive number in sequence and is happy.
> In md3, it got bumped up to drive 2, leaving the drive 0 number unassigned.
This is normal. md puts spare drives in higher slots initially. When the
recovery is done, you'll see the drive move back to its usual slot 0.
--
Paul
next prev parent reply other threads:[~2003-09-04 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 20:37 Minor RAID-1 oddity... any way to fix? linux
2003-09-04 20:43 ` Paul Clements [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-04 21:19 linux
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=3F57A3D7.D3E77710@SteelEye.com \
--to=paul.clements@steeleye.com \
--cc=linux-raid@vger.kernel.org \
--cc=linux@horizon.com \
/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).