|To:||Simon Matter <simon.matter@xxxxxxxxxxxxxxxx>|
|Subject:||Re: Processes stuck in D state..|
|From:||Michael Loftis <mloftis@xxxxxxxxx>|
|Date:||Wed, 06 Aug 2003 13:25:40 -0600|
|Cc:||Gordon Henderson <gordon@xxxxxxxxxx>, linux-xfs@xxxxxxxxxxx|
|References:||<3F283E36.778CC934@xxxxxxxxxx><3F28E34D.3EE2CF4A@xxxxxxxxxxxxxxxx> <3F2920A4.575A310A@xxxxxxxxxx> <Pine.LNX.4.56.0308060851570.25677@xxxxxxxxxxxxxxxxxx> <email@example.com> <38184.108.40.206.140.1060197333.squirrel@xxxxxxxxxxxxxxxxxxxxxxx>|
The whole redhat 2.4.20 kernel is crap. I've had a number of boxes lockup
on it. Initially it was the firewall, but then at home I've had other
boxes lock up under load with it. 2.4.20-19.x got a little better but was
still totally screwed up. Going to a stock 2.4.20 fixed all the issues
I've been having.
The root of this one is IMHO RH 2.4.20 is actually 2.4.21-pre3 plus a mass of patches.
--On Wednesday, August 06, 2003 21:15 +0200 Simon Matter <simon.matter@xxxxxxxxxxxxxxxx> wrote:
Yah for production go with a kernel as close to stock as posible. Avoid anything by redhat in the 2.4.20 series, and you should be fine. In other words go get a fresh treee, patch in ONLY the XFS stuff. Don't put in low latency/preeempt patches, they still screw everything up. And just stay away from RedHate kernels.I don't agree. I'm using XFS enabled RedHat for a long time now on several servers with great success. Are the problem you're talking about always NFS related? That's the only thing I'm not using alot with the XFS boxes. Simon
|<Prev in Thread]||Current Thread||[Next in Thread>|