From: John McMonagle <johnm@advocap.org>
To: Brad Campbell <brad@wasp.net.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: Convert raid5 to raid1?
Date: Thu, 10 Mar 2005 18:02:11 -0600 [thread overview]
Message-ID: <4230E003.4040609@advocap.org> (raw)
In-Reply-To: <4230D279.5090101@wasp.net.au>
Brad
Not saying its broke.
Part of my reasoning to go to raid5 was that I could expand.
While it can be done I don't really see it as practical.
Also it's looking like I probably will not need to expand.
raid5 with 3 drives and 1 spare
or 2 - 2 drive raid1 drives have the same space.
Which is less likely to have a failure cause data loss?
I'm guessing raid1.
If I'm wrong I'd like to know now.
Also concerned about the resync times. It was going to take a couple
days to resync under a rather light load if it weren't for the fact that
it couldn't because of a bad drive and a kernel panic caused by the read
error.
Still not certain about the cause of problem my current guess is the
sata controller.
I'm glad there is work being done on the resync issue.
Also think the ideas to attempt to fix read errors are great.
My only suggestion is that there should be provision to send
notification when it happens.
With both that would really help.
John
Brad Campbell wrote:
> John McMonagle wrote:
>
>> Was planning to adding a hot spare to my 3 disk raid5 array and was
>> thinking if I go to 4 drives I would be a better off as 2 raid1
>> arrays considering the current state of raid5.
>
>
> I just wonder about the comment "considering the current state of
> raid5". What might be wrong with raid5 currently? I certainly know a
> number of people (me included) who run several "large" raid-5 arrays
> and don't have any problems.
>
> Brad
next prev parent reply other threads:[~2005-03-11 0:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 21:38 Convert raid5 to raid1? John McMonagle
2005-03-10 22:34 ` Frank Wittig
2005-03-10 23:04 ` Brad Campbell
2005-03-10 23:13 ` Guy
2005-03-11 0:02 ` John McMonagle [this message]
2005-03-11 3:09 ` Guy
2005-03-11 8:58 ` David Greaves
2005-03-11 0:11 ` Paul Clements
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=4230E003.4040609@advocap.org \
--to=johnm@advocap.org \
--cc=brad@wasp.net.au \
--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).