"VM: do_try_to_free_pages failed for nmbd"
This lovely message was waiting to greet me on all consoles of my debian box when i came in to work this morning, and I can't telnet in. A search on google says:
Upgrade to 2.2.19 , that should fix the problem. It's a bug in the releases between 2.2.14 and 2.2.19, afaik. Has anyone heard of this before? I'm using kernel 2.2.18pre 21, activity on box over weekend should have been minimal apart from backups running. And what were those keys that try to reboot cleanly again? (not the ctl-alt-del) (Hope it isn't going to be one of "those" days....) Nice to meet so many folk yesterday. Jenny.
Upgrade to 2.2.19 , that should fix the problem. It's a bug in the releases between 2.2.14 and 2.2.19, afaik. Has anyone heard of this before? I'm using kernel 2.2.18pre 21, activity on box over weekend should have been minimal apart from backups running.
Yes, .17 and .18 blew up quite spectacularly on tsw a few times. It seems that certain situations end up with swap being consumed and never released. .19 (or maybe .20 now?) cured the problem.
And what were those keys that try to reboot cleanly again? (not the ctl-alt-del)
Hold AltGr and SysRq, then tap out s u u b (sync, unmount, unmount, boot) -- MJR Do you need advice about the Internet or particular net services? Why not talk to my employers? See http://www.luminas.co.uk/ for details.
MJ Ray <markj@cloaked.freeserve.co.uk> writes:
Yes, .17 and .18 blew up quite spectacularly on tsw a few times. It seems that certain situations end up with swap being consumed and never released. .19 (or maybe .20 now?) cured the problem.
And what were those keys that try to reboot cleanly again? (not the ctl-alt-del)
Hold AltGr and SysRq, then tap out s u u b (sync, unmount, unmount, boot)
You should sync after umount too or else you'll probably get spurious fscks on boot (it needs to write a clean umount flag to the superblock) -- http://john.fremlin.de
<ctrl> + <alt> + <del> should reboot cleanly, there is usually a line in /etc/inittab which will catch it and run shutdown. If you compiled the kernel with the sysreq key then there are a number of options however you will still get the fsck's etc... -- Andrew
Jenny_Hopkins@toby-churchill.com writes:
This lovely message was waiting to greet me on all consoles of my debian box when i came in to work this morning, and I can't telnet in.
It's a well-known bug. The VM subsystem was well-and-truly funted in early 2.2 kernels. Upgrade to 2.2.20 (2.2.19 has a security hole), and all should be well. Matthew -- Rapun.sel - outermost outpost of the Pick Empire http://www.pick.ucam.org
participants (5)
-
Andrew Pounce -
Jenny_Hopkins＠toby-churchill.com -
John Fremlin -
Matthew Vernon -
MJ Ray