From: "Kevin P. Fleming" <kpfleming@cox.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Problems and questions with LVM on a large raid system.
Date: Wed Mar 12 17:25:01 2003 [thread overview]
Message-ID: <3E6FC1C0.9040204@cox.net> (raw)
In-Reply-To: <20030312231627.GA15246@gw.silicide.dk>
jon+lvm@silicide.dk wrote:
> On Wed, Mar 12, 2003 at 03:59:57PM -0700, Kevin P. Fleming wrote:
>
>>jon+lvm@silicide.dk wrote:
>>
>>>you're talking about raid0. You dont rebuild raid0. Not in hardware, not
>>>in software.
>>
>>OK, I missed that extremely important and very obvious point :-)
>
>
> thought so. Anyway, why would it take longer time to rebuild the
> array using software rather than hardware raid? It's still the
> same ammount of data needed to be copied.
>
Right, but a kernel oops doesn't cause an array rebuild to be necessary if
you're using a 3ware or similar RAID card. The only thing that would cause a
rebuild would be a drive failure or a power failure (which is of course easy to
protect against).
The software code (which I've been using for quite a while) needs to rebuild any
time the array is not shut down cleanly, which can happen for a number of reasons.
next prev parent reply other threads:[~2003-03-12 17:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 13:53 [linux-lvm] Problems and questions with LVM on a large raid system Petro
2003-03-12 16:14 ` jon+lvm
2003-03-12 16:24 ` Kevin P. Fleming
2003-03-12 16:50 ` jon+lvm
2003-03-12 17:00 ` Kevin P. Fleming
2003-03-12 17:17 ` jon+lvm
2003-03-12 17:25 ` Kevin P. Fleming [this message]
2003-03-12 17:46 ` Petro
2003-03-13 2:44 ` Jon Bendtsen
2003-03-13 18:25 ` Petro
2003-03-14 2:32 ` Adrian Phillips
2003-03-15 13:50 ` Steven Lembark
2003-03-15 16:37 ` jon+lvm
2003-03-18 3:14 ` Heinz J . Mauelshagen
-- strict thread matches above, loose matches on Subject: below --
2003-03-12 21:03 Barry, Christopher
2003-03-13 2:45 ` Jon Bendtsen
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=3E6FC1C0.9040204@cox.net \
--to=kpfleming@cox.net \
--cc=linux-lvm@sistina.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.