From: Paul Clements <Paul.Clements@SteelEye.com>
To: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
Cc: Stef Telford <stef@chronozon.artofdns.com>, linux-raid@vger.kernel.org
Subject: Re: Software RAID level 1 issue
Date: Fri, 30 May 2003 18:04:59 -0400 [thread overview]
Message-ID: <3ED7D58B.984C6A17@SteelEye.com> (raw)
In-Reply-To: 20030530214457.GT20195@rdlg.net
"Robert L. Harris" wrote:
>
> The problem I see and I believe I've had is when the box starts to boot
> up the system hangs durring the init script runs (pre-runlevel 3). At
> these times my system is busy hammering my raid arrays and will finally
> continue on to run level 3 once things are synced up.
Hmm, could it be fsck on a busily resyncing array? It must be something
in the initscripts that is causing this...the driver's raidstart command
will return and give you access to the device before (while) the resync
begins...
Is this on Red Hat?
--
Paul
> Thus spake Stef Telford (stef@chronozon.artofdns.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>
> >
> > -
> > 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
>
> :wq!
> ---------------------------------------------------------------------------
> Robert L. Harris | GPG Key ID: E344DA3B
> @ x-hkp://pgp.mit.edu
> DISCLAIMER:
> These are MY OPINIONS ALONE. I speak for no-one else.
>
> Diagnosis: witzelsucht
>
> IPv6 = robert@ipv6.rdlg.net http://ipv6.rdlg.net
> IPv4 = robert@mail.rdlg.net http://www.rdlg.net
>
> ------------------------------------------------------------------------
> Part 1.2Type: application/pgp-signature
next prev parent reply other threads:[~2003-05-30 22:04 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 ` Software RAID level 1 issue Stef Telford
2003-05-30 21:44 ` Robert L. Harris
2003-05-30 22:04 ` Paul Clements [this message]
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 Greg Rasberry
2003-05-30 17:53 Adriana 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=3ED7D58B.984C6A17@SteelEye.com \
--to=paul.clements@steeleye.com \
--cc=Robert.L.Harris@rdlg.net \
--cc=linux-raid@vger.kernel.org \
--cc=stef@chronozon.artofdns.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).