Re: "0-order allocation failed"

[Arjen Wolfs <arjen@xxxxxxxx>]

At 07:40 PM 8/19/2001, you wrote:

> We're building a server for a CVS repository consisting of several tens
> of thousands of files; about 1.5GB of data total.  It's a two-processor
> Pentium-III machine with a Mylex RAID controller and 4GB of RAM.
>
> We installed from the RH7.1/XFS 1.0.1 media, built a 2.4.5 kernel with
> the XFS 1.0.1 patches, copied the repository into place and ran a small
> script that copied the repository four times, copied the resulting directory,
> then removed both copies.
>
> I let it run overnight -- came in this morning to find that the first time
> I ran any command that generated any disk I/O on the box, I got dozens of
> "0 order alloc failed" messages on the console and then a hard hang.
>
> I see mention of this bug in a list message from April, but nothing since
> then.  Has it been fixed, or even analyzed?  If it's been fixed, is there a
> simple patch against 1.0.1 or will I need to run the latest from CVS?


Hi,

I've had the sampe problem with highmem+smp kernels, random hangs and 
0-order allocation failed messages. The first version that worked for me 
was the patch against 2.4.7; it's been very stable so far. Give it a try...

Arjen Wolfs