From: Helge Hafting <helgehaf@aitel.hist.no>
To: Brad Chapman <jabiru_croc@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [QUESTION] Is 2.5.41 useable?
Date: Wed, 09 Oct 2002 09:35:01 +0200 [thread overview]
Message-ID: <3DA3DC25.F383E92D@aitel.hist.no> (raw)
In-Reply-To: 20021008105729.79814.qmail@web40019.mail.yahoo.com
Brad Chapman wrote:
>
> Sir,
>
> --- jbradford@dial.pipex.com wrote:
> > > Is 2.5.41 useable, i.e. will it mostly work without Oopsing or crashing?
> >
> > It is way too soon for anybody to be able to say - it's only been released
> > for a day!
>
> Hmmm. Perhaps I should have asked the question, "Does 2.5.41 contain any code
> that would be likely to impact performance or stability?"
Depends on what you use. Much of 2.5.41 is great, but RAID is
broken in several ways:
1. raid-0 simply doesn't work. There is an excellent patch
fixing it, but it isn't in 2.5.41.
2. raid-1 kills the kernel after a minute or so
if it need to resync a array big enough to take that much
time with my 20MB/s disks.
If you need a "big" resync, reboot to something safe like 2.5.7
or earlier.
3. raid-1 on the root is always dirty needing a resync after shutdown,
so a root-raid1 had better be "small". Or you can't boot it.
This should not bother you if you don't use software raid.
The nfs client have some trouble too, see the thread called
"invalidate_inode_pages". I were unable to reproduce
my problems on 2.5.41 so perhaps it is fixed and I
missed the announcement.
Again, nothing to worry about if you don't use a nfs client.
2.5.41 seems just fine otherwise for my uses.
Helge Hafting
prev parent reply other threads:[~2002-10-09 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 22:01 [QUESTION] Is 2.5.41 useable? Brad Chapman
2002-10-08 9:49 ` jbradford
2002-10-08 10:57 ` Brad Chapman
2002-10-08 11:41 ` jbradford
2002-10-09 7:35 ` Helge Hafting [this message]
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=3DA3DC25.F383E92D@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=jabiru_croc@yahoo.com \
--cc=linux-kernel@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