search for: bufobj

My server just literally was brought to it's knees with this message spewing on the console: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 1203133, size: 4096 (blkno and size were varying) Some searching says that this is or was a bug. Has this been fixed yet? If so, what should I upgrade to? I'm currently running 6.3 Michael Grant

...them on the new server and started to decompress the files. Www data have been decompressed correctly on the ISCSI disk. But while the messages were being decompressed (~80GB of tar.gz) and all the DB were being restored, the server crashed. The error shown was: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 31, size: 4096 This message repeated every 30 seconds. While restarting with the single user mode I checked there wasn't any message after the crash in /var/log/messages. I think 1GB of swap should be enough, since with this configuration on FreeBSD 5.5 everything worked for over 2...

...d memory (256M), but I''ve compensated with swap space (1G) Now anytime I''m putting the system under stress, by building ports or by running a git clone on the kernel repository here, I''m seeing a lot of messages about swap_pager: > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 132545, size: 4096 The system also becomes very sluggish and sometimes unresponsive. The weird thing was that one of these messages happened right after a reboot when I rebuilt an outdated port and on the main console was checking the swap memory: > jeroen:~/ $ swapinfo...

...to page in work fine. (You can hit return in a shell, get another login: prompt on other consoles, and the like.) The system continues to respond to pings, but anything that attempts to do a disk IO simply stops. Sometimes the kernel emits messages like this: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 2, size: 4096 The test we are using to produce this "hang" is a fairly trivial expansion of a tar ball being fed via nc from another system. We run on the source system: tar cf - radar | nc -w 3 10.10.10.229 12345 And on the system being tested we run: nc -l 12345 |...