Hi,
We have the following configuration.
Control domain, one alternate IO domain, one guest domain with storage
services exported form control and alternate IO domain.
LDom version is 2.0.
Storage exported to guest domain for boot disk are as follows:
1.Created a flat file on control domain, exported to guest domain as
vdisk.
2. Created a flat file on alternate IO domain, exported to guest domain
as vdisk.
On guest domain, created a mirrored boot disk configuration using the
above two disks.
When one of the flat file used as back end device is not available
(either because file system containing flat file not mounted or any
other reason), guest domain work fine with mirrored volume.
But the issue we are facing is, when the this flat file is brought
available, guest domain do not detect it even after trying `devfsadm
-Cv` commands, unless guest domain is stopped, unbind, bind and started
again.
O/P even when back end devices are available:
bash-3.00# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0d0 <drive type unknown>
/virtual-devices@100/channel-devices@200/disk@0
1. c0d1 <SUN-DiskImage-9GB cyl 261 alt 2 hd 96 sec 768>
/virtual-devices@100/channel-devices@200/disk@1
Specify disk (enter its number):
Because of this if the second mirrored disk become unavailable, though
first disk (flat file on control or alternate io domain) is brought
available guest domain will be unusable.
This issue is only seen when flat files are used as back end device and
not with raw devices or LUNS.
So when backend storage device is flat file, why does ldom fail to
detect its availability at run time?
Thanks & Regards,
Sajith
_______________________________________________
ldoms-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
