If a disk is part of an SVM metaset then that means this disk is expected to be used by SVM so you probably you shouldn't export that disk as a virtual disk. Also a disk in a SVM metaset as a special partitioning.
For example, when a disk is part of a SVM metaset then SVM reserves the disk using SCSI reservations, so if you issue your own SCSI reservation commands then you are going to confuse SVM and enter an unexpected state. When using VxDMP, you should use the disk as managed by VxDMP (i.e. /dev/vx/dmp/dsk/...) and not the physical disk itself (/dev/dsk/...) alex. On 02/18/09 09:23, Steffen Weiberle wrote: > On 02/18/09 11:37, Rushi Srinivas wrote: >> I want to issue scsi commands on the vdisk backend (lun) in the >> service domain, where the exported vdisk is part of SVM metaset in >> guest domain. >> >> But, I came across a note in LDom 1.1 Admin guide, which says >> "applications running in the service domain and in guest domains >> should not issue SCSI commands to the same physical SCSI disks; >> otherwise, this can lead to an unexpected disk state" >> >> Hence, If I use SVM metaset or VxDMP in the guest domains, (which also >> use scsi commands) and issue scsi commands on the same SCSI disks in >> service domains, will my disk go into an unexpected state?? > > I imagine any two OS instances each issuing SCSI commands separately to > the same target device could lead to unexpected states on the target > device. I can't see how the target being part of an SVM metaset would > make a difference in one OS instance not knowing that the device had > been 'changed' by another OS instance. > > Steffen > >> >> TIA, >> Rushi > > _______________________________________________ > ldoms-discuss mailing list > ldoms-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
