From: Mike Tran <mhtran@us.ibm.com>
To: linux-raid@vger.kernel.org
Subject: Re: EVMS or md?
Date: Mon, 04 Apr 2005 18:03:33 -0500 [thread overview]
Message-ID: <1112655813.7245.10.camel@langvan2.homenetwork> (raw)
In-Reply-To: <d2seal$ntf$1@terminus.zytor.com>
On Mon, 2005-04-04 at 17:15, H. Peter Anvin wrote:
> Followup to: <200504041446.50337.kewley@gps.caltech.edu>
> By author: David Kewley <kewley@gps.caltech.edu>
> In newsgroup: linux.dev.raid
> >
> > Mike Tran wrote on Monday 04 April 2005 12:28:
> > > We (EVMS team) intended to support RAID6 last year. But as we all
> > > remember RAID6 was not stable then. I may write a plugin to support
> > > RAID6 soon.
> >
> > Hi Mike,
> >
> > In your view, is RAID6 now considered stable? How soon might you have an evms
> > plugin for it? ;) I'd love to use evms on my new filserver if it supported
> > RAID6.
> >
I will do it, but I can't promise a time frame. I will announce on evms
mailing list when it's available. This discussion should be on evms
mailing list (sorry folks!)
>
> I can't speak for the EVMS people, but I got to stress-test my RAID6
> test system some this weekend; after having run in 1-disk degraded
> mode for several months (thus showing that the big bad "degraded
> write" bug has been thoroughly fixed) I changed the motherboard, and
> the kernel didn't support one of the controllers. And now there were
> 2 missing drives. Due to some bootloader problems, I ended up
> yo-yoing between the two kernels a bit more than I intended to, and
> went through quite a few RAID disk losses and rebuilds as a result.
>
> No hiccups, data losses, or missing functionality. At the end of the
> whole ordeal, the filesystem (1 TB, 50% full) was still quite prisine,
> and fsck confirmed this. I was quite pleased :)
>
> Oh, and doing the N-2 -> N-1 rebuild is slow (obviously), but not
> outrageously so. It rebuilt the 1 TB array in a matter of
> single-digit hours. CPU utilitization was quite high, obviously, but
> it didn't cripple the system by any means.
>
Glad to hear the good news :) mdadm or EVMS is just a user space tool.
We depend on the kernel side to provide stability.
--
Mike T.
next prev parent reply other threads:[~2005-04-04 23:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 2:52 raidreconf / growing raid 5 doesn't seem to work anymore Mike Hardy
2005-04-04 5:48 ` David Greaves
2005-04-04 7:08 ` EVMS or md? Guy
2005-04-04 7:57 ` David Greaves
2005-04-04 19:28 ` Mike Tran
2005-04-04 21:46 ` David Kewley
2005-04-04 22:15 ` H. Peter Anvin
2005-04-04 22:52 ` Gordon Henderson
2005-04-04 23:03 ` Mike Tran [this message]
2005-04-05 6:17 ` Brad Campbell
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=1112655813.7245.10.camel@langvan2.homenetwork \
--to=mhtran@us.ibm.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).