Bug#636306: mount.nfs: page allocation failure. order:4, mode:0xc0d0

2012-06-08 Thread Jonathan Nieder
tags 636306 - moreinfo forcemerge 657078 636306 quit Ben Hutchings wrote: > Although the new idmapper may be the way forward, we're stuck with the > old implementation for now. We should still be able to get rid of the > huge allocation though. Ah, didn't notice this was already filed. Merging

Bug#636306: mount.nfs: page allocation failure. order:4, mode:0xc0d0

2011-10-26 Thread Berni Elbourn
On 24/10/11 16:24, Anders Boström wrote: Hi! We have got this problem on a NFS-server running Debian stable amd64. The server has 8Gbyte memory and at times quite high load, but mostly NFSv3. However, I can't experiment with the patch, this server is too important and it is hard to schedule ser

Bug#636306: mount.nfs: page allocation failure. order:4, mode:0xc0d0

2011-10-24 Thread Anders Boström
Hi! We have got this problem on a NFS-server running Debian stable amd64. The server has 8Gbyte memory and at times quite high load, but mostly NFSv3. However, I can't experiment with the patch, this server is too important and it is hard to schedule service-windows. / Anders -- To UNSUBSCRI

Bug#636306: mount.nfs: page allocation failure. order:4, mode:0xc0d0

2011-09-07 Thread Berni Elbourn
The trick to do "task || task" in cron did work several times. I am very grateful but (would you believe it) only yesterday the system was moved onto something with far more memory. :-( I doubt it will suffer the problem again. If this becomes an issue for others I would be happy to set-up a

Bug#636306: mount.nfs: page allocation failure. order:4, mode:0xc0d0

2011-09-06 Thread Ben Hutchings
On Wed, 2011-08-10 at 08:44 +0100, Berni Elbourn wrote: > Instead of switching to cifs, I tried swapiness=100, and just doubling > up on the backup job: > > 25 23 * * * disk-backup || (sleep 100; disk-backup) > > Last night the first backup failed, second backup worked. Yippee. > > The first ba

Bug#636306: mount.nfs: page allocation failure. order:4, mode:0xc0d0

2011-08-10 Thread Berni Elbourn
Instead of switching to cifs, I tried swapiness=100, and just doubling up on the backup job: 25 23 * * * disk-backup || (sleep 100; disk-backup) Last night the first backup failed, second backup worked. Yippee. The first backup failed by a simple test for the presence of a file the nfs mount.

Bug#636306: mount.nfs: page allocation failure. order:4, mode:0xc0d0

2011-08-02 Thread Berni Elbourn
On 02/08/11 11:49, Ben Hutchings wrote: Does this system have swap enabled? Afraid so... elbournb@sv22:~$ free -m total used free sharedbuffers cached Mem: 184172 11 0 5 69 -/+ buffers/cache: 98

Bug#636306: mount.nfs: page allocation failure. order:4, mode:0xc0d0

2011-08-02 Thread Ben Hutchings
On Tue, 2011-08-02 at 11:49 +0100, Ben Hutchings wrote: > On Tue, 2011-08-02 at 08:13 +0100, Berni Elbourn wrote: [...] > > A "missing" parameter is mentioned here: > > > > https://lkml.org/lkml/2011/2/24/73 > [...] > > I can't see what you're referring to in that message. Sorry, I didn't origin

Bug#636306: mount.nfs: page allocation failure. order:4, mode:0xc0d0

2011-08-02 Thread Ben Hutchings
On Tue, 2011-08-02 at 08:13 +0100, Berni Elbourn wrote: > Package: linux-2.6 > Version: 2.6.32-35 > Severity: normal > > > The mount failure occures on this system about 1 in 10. Subsequent > mounts work just fine. This never happened on Lenny. Sorry if this is > a duplicate but bts was down whe

Bug#636306: mount.nfs: page allocation failure. order:4, mode:0xc0d0

2011-08-02 Thread Berni Elbourn
Package: linux-2.6 Version: 2.6.32-35 Severity: normal The mount failure occures on this system about 1 in 10. Subsequent mounts work just fine. This never happened on Lenny. Sorry if this is a duplicate but bts was down when I ran reportbug. Google seems to go for this: https://bugzilla.redh