Attached a long series of order 1 (!) page allocation failures with .33-rc7 
on an arm NAS box (running Debian unstable).

The first failure occurred while running aptitude (Debian package manager) 
only ~20 minutes after booting the system, and I've seen that happen twice 
before.

The other failures were all 1.5 days later while rsyncing a lot of music 
files (ogg/mp3) from another box to this one.
They occurred when I was trying to also do something in an SSH session. The 
first ones from a simple 'sudo vi /etc/exports', some of the later ones 
while creating a new SSH session from my laptop.

As can be seen from the attached munin graph [1] the system has only 256 MB 
memory, but that's quite normal for a simple NAS system. Only very little 
of that was in use by apps; most was being used for cache.
The errors occurred in the area immediately above the "Thu 12:00" label, 
where the cache increases dramatically.

Isn't it a bit strange that cache claims so much memory that real processes 
get into allocation failures?

Cheers,
FJP

[1] munin was running in the background and may well have contributed to 
some of the allocation failures. During most of the rsync it was the only 
significant other process running. But munin was not yet installed when 
the first allocation failure (for aptitude) occurred.