From: Bryan Whitehead <driver@jpl.nasa.gov>
To: martin f krafft <madduck@madduck.net>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: RAID 5 from 2.4.24 to 2.6.0
Date: Thu, 08 Jan 2004 10:14:15 -0800 [thread overview]
Message-ID: <3FFD9DF7.6030508@jpl.nasa.gov> (raw)
In-Reply-To: <20040108171520.GA19872@piper.madduck.net>
martin f krafft wrote:
>>You'd better use 2.6.1-rc1 or later if you want to actually use
>>the arrays.
>
>
> So I take it there are great improvements coming, and my problems[1]
> could well be fixed by that... well, sounds like it's worth a try!
>
> 1. http://marc.theaimsgroup.com/?l=linux-kernel&m=107357557927500&w=2
>
Can you run memtest on this box with stability problems?
--
Bryan Whitehead
SysAdmin - JPL - Interferometry and Large Optical Systems
Phone: 818 354 2903
driver@jpl.nasa.gov
next prev parent reply other threads:[~2004-01-08 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 13:43 RAID 5 from 2.4.24 to 2.6.0 Martin F Krafft
2004-01-08 13:55 ` Måns Rullgård
2004-01-08 17:15 ` martin f krafft
2004-01-08 18:14 ` Bryan Whitehead [this message]
2004-01-09 8:57 ` martin f krafft
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=3FFD9DF7.6030508@jpl.nasa.gov \
--to=driver@jpl.nasa.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=madduck@madduck.net \
/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