From: Tyler <pml@dtbb.net>
To: "David M. Strang" <dstrang@shellpower.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Rebuilt Array Issue
Date: Thu, 11 Aug 2005 04:31:27 -0700 [thread overview]
Message-ID: <42FB370F.6000800@dtbb.net> (raw)
In-Reply-To: <003701c59e5d$fbbc5ca0$c700a8c0@NCNF5131FTH>
David M. Strang wrote:
<snip...>
> 24 65 128 24 active sync
> /dev/scsi/host2/bus0/target24/lun0/disc
> 25 65 144 25 active sync
> /dev/scsi/host2/bus0/target25/lun0/disc
> 26 0 0 - removed
> 27 65 176 27 active sync
> /dev/scsi/host2/bus0/target27/lun0/disc
>
> 28 65 160 26 active sync
> /dev/scsi/host2/bus0/target26/lun0/disc
>
>
> Is it supposed to stay with number 26 as removed forever? Does number
> 28 ever jump back up to that spot? I shouldn't have to hotadd and
> allow it to resync everytime I re-assemble the raid should I?
>
No, you shouldn't have to hotadd and resync each time, after hot-adding
a "new" device and the initial rebuild finishes, unless there's another
failure after that, or an unclean shutdown.
Tyler.
prev parent reply other threads:[~2005-08-11 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 10:18 Rebuilt Array Issue David M. Strang
2005-08-11 11:28 ` Tyler
2005-08-11 11:31 ` Tyler [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=42FB370F.6000800@dtbb.net \
--to=pml@dtbb.net \
--cc=dstrang@shellpower.net \
--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).