Hi Bob,
The problem could be due to a faulty/failing disk, a poor connection
with a disk, or some other hardware issue. A failing disk can easily
make the system pause temporarily like that.
As root you can run '/usr/sbin/fmdump -ef' to see all the fault events
as they are reported. Be sure to execute '/usr/sbin/fmadm faulty' to
see if a fault has already been identified on your system. Also
execute '/usr/bin/iostat -xe' to see if there are errors reported
against some of your disks, or if some are reported as being
abnormally slow.
You might also want to verify that your Solaris 10 is current. I
notice that you did not identify what Solaris 10 you are using.
Thanks a lot for these hints. I checked all this. On my mirror server I
found a faulty DIMM with these commands. But on the main server
exhibiting the described problem everything seems fine.
another machine with 6GB RAM I fired up a second virtual machine
(vbox). This drove the machine almost to a halt. The second vbox
instance never came up. I finally saw a panel raised by the first
vbox instance that there was not enough memory available (non severe
vbox error) and the virtual machine was halted!! After killing the
process of the second vbox I could simply press resume and the first
vbox machine continued to work properly.
Maybe you should read the VirtualBox documentation. There is a note
about Solaris 10 and about how VirtualBox may fail if it can't get
enough contiguous memory space.
Maybe I am lucky since I have run three VirtualBox instances at a time
(2GB allocation each) on my system with no problem at all.
I have inserted
set zfs:zfs_arc_max = 0x200000000
in /etc/system and rebooted the machine having 64GB of memory. Tomorrow
will show whether this did the trick!
Thanks a lot,
Andreas
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
