Hi,
I double checked the configuration with xm and the "w!" option seems to
be configured :-(
I also upgraded to build 123, but also no change in behaviour. Thus is
this a RAC 11.2
problem or is there a general problem using zvols as as shared disks for
xVM domains ?
(device
(vbd
(protocol x86_64-abi)
(uuid 048d282d-da4c-2e0b-b9f4-f3f4cc0811c7)
(dev xvdc:disk)
(uname phy:/dev/zvol/dsk/rpool/export/xvm/asm1)
(mode 'w!')
(backend 0)
(bootable 0)
(VDI )
)
)
(device
(vbd
(protocol x86_64-abi)
(uuid 078a81f8-76f3-cb82-ab43-91169ff7d4b7)
(dev xvdd:disk)
(uname phy:/dev/zvol/dsk/rpool/export/xvm/asm2)
(mode 'w!')
(backend 0)
(bootable 0)
(VDI )
)
)
--- Begin Message ---
Hi,
I just tried to setup a fresh Oracle RAC 11.2. For this reason I created
two paravirtualized
guests running Oracle unbreakeable Linux 5.3 64 bit. Each guest owns a
private disk (zvol)
and is connected to two shared disks (also zvols):
<disk type='block' device='disk'>
<driver name='phy'/>
<source dev='/dev/zvol/dsk/rpool/export/xvm/asm1'/>
<target dev='xvdc' bus='xen'/>
* <shareable/>*
</disk>
<disk type='block' device='disk'>
<driver name='phy'/>
<source dev='/dev/zvol/dsk/rpool/export/xvm/asm2'/>
<target dev='xvdd' bus='xen'/>
*<shareable/>*
</disk>
However the shareable tag seems to be ignored. When the second node
tries to join the cluster the
CRS diskmon returns a timeout. I think this is because the first node
locks the shared disk exclusively.
In other XEN environments the tag "w!" is used to enable shared access
to a disk. As I did not find
any hint in terms of this issue in xVM I assumed "shareable" could be
the solution, but obviously it
isn't. So how to solve this issue ind xVM on Opensolaris ? Is there an
easy xVM internal solution or
do I need to use iSCSI ?
Many thanks, Marc
--- End Message ---
_______________________________________________
xen-discuss mailing list
[email protected]
