You still may have a potential disk problem, which (assuming it is part of your root filesystem/zpool) could explain the hangs. I'm not convinced that this is either a NIC/network or memory related problem.
Usually it is wise to fix any obvious faults first, and the disk problems are obvious faults. The "device is gone" strikes me as a message that would ultimately stop the system in its tracks unless the device comes back. That would certainly account for a hang.
[ Incidentally, the best system I've seen which managed without a root filesystem was an E10k domain. When we eventually got the call here at Sun, we determined that the last remaining root filesystem mirror disk had disappeared 26 hours prior to the system grinding to a halt. Goodness knows how it managed for so long before finally giving up, but I was rather impressed :-) ]
Regards, Brian CF wrote:
Thanks for replying, Brian. It's correct that I pushed the reset button, the computer was unresponsive. After rebooting once more, the NIC returned. I've been looking over the different components, and found that my Dom0 were allocated all of my RAM, and I suspect this is the cause. I've transferred a few hundred GBs over the LAN and external disks, with no performance issues. After reducing the memory allocated to the xen hypervisor, the system gradually freed up more memory. However, if I reduce it to <500MB - even with no virtual machines running - my computer hangs terribly, and swap usage sky rockets. I had no idea that it was using memory without any VMs running, I need to do some research here.. Again, thanks for replying.
-- Brian Ruthven Sun Microsystems UK Solaris Revenue Product Engineering Tel: +44 (0)1252 422 312 Sparc House, Guillemont Park, Camberley, GU17 9QG _______________________________________________ opensolaris-discuss mailing list [email protected]
