Date: Thu, 29 Mar 2012 13:53:49 -0400 From: "Dieter BSD" <dieterbsd@engineer.com> To: freebsd-hackers@freebsd.org Subject: Re: Please help me diagnose this crazy VMWare/FreeBSD 8.x crash Message-ID: <20120329175350.155040@gmx.com>
next in thread | raw e-mail | index | archive | help
> FreeBSD ?? - 7.4 never crash > FreeBSD 8.0 - 8.2 crashes Obvious short term workaround is to run production on 7.4 (assuming you can) until you figure out what is wrong with 8.x. What filesystem(s) are you running? UFS? ZFS? other? > started randomly disconnecting people every morning Due to timeouts? Something might be keeping interrupts disabled too long. > there were other good reasons to reload the > VM, so I nuked the VM, which, of course, fixed it. > I can look at recovering the faulty VM from backup Sounds like corruption. Can you compare the bad VM against a good one? If you find corruption, the question then becomes what is causing the corruption? Sounds like the same thing is getting corrupted every time, rather than something at random. Sounds like the corruption is causing a deadlock in something common, like the buffer cache, or filesystem, or... Is it possible to have root be a ramdisk? This might give you access to the utilities, depending on where the problem is. I have vague memories that the sticky bit used to lock a program in memory, but sticky(8) indicates that this is no longer the case. Is there a way to lock a program in memory? (So that it will be available when the system can't do disk i/o.) If not, you could keep some windows open with things like top and systat -vmstat running. Some of the utilities have options to look at a disk file rather than the live system, if you can get a core dump (swap to NFS?).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120329175350.155040>