When you shutdown the primary domain, there's probably
a window during which the guest domain is still connected
to the primary domain but the CFS mount with the disk images
has been unmounted (as part of the shutdown process).
During that window, the vdisk will not failover because the
guest can still connect the vds, however vdisk I/O will fail
because the backend is not accessible anymore.
This problem should be solved with the fix for 6726533 (vdisk
failover should handle storage/storage-path failures) which
will be available in the next update of Solaris.
alex.
On 08/25/10 10:11, Buck Huffman wrote:
Whenever I shutdown my primary domain, the guest ldoms are getting i/o errors
when it tries to write to its boot disk or run certain commands. I have
secondary domains setup and the boot disks are setup in a mpgroup. My boot
disk images are running on a CFS mount that the primaries and secondaries have
mounted (2 5440's w/ 2 i/o domains - so a 4 node cluster). Is there a log to
show the mpgroup fail over?
I'm looking at the LDOM I/O BP manual and the only difference I can see with my configuration is the secondary domains use the same mount point and the primary.
LDOM BP config:
# ldm add-vdsdev mpgroup=red /domains/vdisk0.img v...@secondary-vds0
# ldm add-vdsdev mpgroup=red /vdisks/vdisk0.img v...@primary-vds0
# ldm add-vdisk vdisk0 v...@secondary-vds0 guest
Mine:
ldm add-vdsdev mpgroup=oracledisk0 /domains/donald-oracle di...@primary-vds0
ldm add-vdsdev mpgroup=oracledisk0 /domains/donald-oracle di...@secondary-vds0
ldm add-vdisk vdisk0 di...@primary-vds0 oracle
What can cause the ldom to get these i/o errors when the primary reboots?
_______________________________________________
ldoms-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
