[EMAIL PROTECTED] wrote on 05/13/2005 04:40:43 AM:
> Couple of messages from the log:
>
> __alloc_pages: 1-order allocation failed
> __alloc_pages: 0-order allocation failed
We used to see this when we were running our own 2.4.24 kernel builds from kernel.org. I can't find the exact errors anymore, but I think we saw (at least) the 0-order error.
We've now moved to RHEL 3 and things are running fine with no memory errors.
> Exactly why this system is running out of memory has yet to be
> established, but it seems to
> also cause one or two JFS filesystems to turn read-only? Which in
> turn only exacerbates the problem.
> Is this intentional behaviour?
I don't think we saw JFS go read-only in this case, but eventually the systems would become unresponsive and we were agressively rebooting for a while.
Bill Marshall
IBM Global Services Unix & Intel Servers
Rochester PC Server Team
Building 020-3, Rochester, MN
- [Jfs-discussion] Failure to allocate memory leaves file-s... Per Jessen
- Re: [Jfs-discussion] Failure to allocate memory leav... Dave Kleikamp
- Re: [Jfs-discussion] Failure to allocate memory ... Per Jessen
- Re: [Jfs-discussion] Failure to allocate mem... Dave Kleikamp
- Re: [Jfs-discussion] Failure to allocate... Per Jessen
- William Marshall
