From: Stef Telford <stef@chronozon.artofdns.com>
To: Paul Clements <Paul.Clements@SteelEye.com>, linux-raid@vger.kernel.org
Subject: Re: Software RAID level 1 issue
Date: 31 May 2003 15:39:33 -0400 [thread overview]
Message-ID: <1054409970.14937.296.camel@testlin.hades> (raw)
In-Reply-To: <3ED7B898.4409555F@SteelEye.com>
Paul Clements wrote:
> Stef Telford wrote:
>
> [snip]
>
> > during resync's on raid-1 the mirror will not be available.
>
> I'm not sure I understand this. md/raid1 devices are accessible while
> resync is occurring...albeit with lower I/O throughput since the resync
> is consuming bandwidth.
>
The way i read the original posters question was
that he/she was trying to restart the faulted
'device', or rather was trying to re-activate the
broken md device whilst the working copy was trying to
rebuild it. accessing the working copy should work, but
not the broken md (unless i have seriously misread
someplace :). Under raid5 or raid10, you can still
access the broken md during a resync/rebuild, this
was what i thought the person was trying to do.
apologies if i misunderstood the original phrasing :)
regards
Stef Telford <stef@chronozon.artofdns.com>
next prev parent reply other threads:[~2003-05-31 19:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-30 18:28 Software RAID level 1 issue Brian Schwarz
2003-05-30 18:40 ` Robert L. Harris
2003-05-31 17:44 ` Stef Telford
2003-05-30 20:01 ` Paul Clements
2003-05-30 20:12 ` 3tcdgwg3
2003-05-30 20:31 ` Paul Clements
2003-06-02 18:10 ` 3tcdgwg3
2003-06-02 18:16 ` Paul Clements
2003-11-07 7:29 ` Software RAID level performance 3tcdgwg3
2003-05-31 19:39 ` Stef Telford [this message]
2003-05-30 21:44 ` Software RAID level 1 issue Robert L. Harris
2003-05-30 22:04 ` Paul Clements
2003-05-30 23:32 ` Robert L. Harris
2003-05-31 20:21 ` Gregory Leblanc
-- strict thread matches above, loose matches on Subject: below --
2003-05-30 17:53 Adriana Rasberry
2003-05-30 17:53 Greg Rasberry
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=1054409970.14937.296.camel@testlin.hades \
--to=stef@chronozon.artofdns.com \
--cc=Paul.Clements@SteelEye.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;
as well as URLs for NNTP newsgroup(s).