search for: 36079

...handle on it. Basically, the box runs idle but refuses to do disk IO, or does it -very- slowly. Top shows processes stuck in 'ffsvget', 'inode', and 'vlruwk' state. I can get the box responsive again by setting sysctl kern.maxvnods=100000. It starts up with kern.maxnodes=36079. I don't know yet if this is a 'fix' - I wanted to send this mail out before the box froze again. I can reliably get the box in to this state by doing 'find /'. I do have a lot of files on the disk, and a things like squid and postgres that do a lot of file i/o, but I don'...

...77, stackpage=c28b7000) Stack: c020213b c020227f 00000045 00000000 00000200 0000050c c28b7e8c 00000000 c013251e c2099900 00000000 c2e7d7c0 00000001 c2099900 00000000 0000050c 00000000 c28b7f54 00000513 00000000 c28d5000 c2e7d7c0 00000200 00000000 Call Trace: [tvecs+35755/73400] [tvecs+36079/73400] [__block_prepare_write+238/544] [cont_prepare_write+473/736] [fat_get_block+0/288] [fat_prepare_write+38/48] [fat_get_block+0/288] [generic_file_write+929/1344] [default_fat_file_write+34/96] [fat_file_write+45/64] [sys_write+214/256] [system_call+52/64] [startup_32+43/310] Code: 0f 0...

Anyone can help? I continue without access from server: /etc/cron.daily/freshclam: ERROR: No servers could be reached. Giving up ERROR: No servers could be reached. Giving up ERROR: No servers could be reached. Giving up ERROR: No servers could be reached. Giving up ERROR: No servers could be reached. Giving up ERROR: No servers could be reached. Giving up ERROR: Update failed. Your network may