Hello:
Has anyone ever tried this and succeeded or found a work-around?
Configuration:
- Solaris 10 x86 (HW 06/06 patched) implemented inside VMWare Server 1.0.1
- Veritas Storage Foundation 4 Basic (latest) inside the same Virtual machine.
- Provision several VMWare based "*.vmdk" disks for Volume Manager to use.
The problem is that Volume Manager complains that "Disk sector size is not
supported" when I try to initialize the VMWare based disks for use with
Volume Manager. See below:
[EMAIL PROTECTED] vxdisk list
DEVICE TYPE DISK GROUP STATUS
c1t0d0s2 auto:none - - online invalid (O/S
disk)
-- (below are the additional "*.vmdk" disks I configured for VxVM to use) --
c1t1d0s2 auto:none - - online invalid
c1t2d0s2 auto:none - - online invalid
c1t3d0s2 auto:none - - online invalid
c1t4d0s2 auto:none - - online invalid
c1t5d0s2 auto:none - - online invalid
c1t6d0s2 auto:none - - online invalid
c1t8d0s2 auto:none - - online invalid
----------------------------------------------------------------------------
[[SO FAR SO GOOD ABOVE - "online invalid" is ok at this stage]]
[[ NEXT IS THE PROBLEM ]]
[EMAIL PROTECTED] vxdisksetup -i c1t1d0 privlen=8192
VxVM vxdisk ERROR V-5-1-5433 Device c1t1d0s2: init failed:
Disk sector size is not supported
[[ ABOVE ERROR IS THE PROBLEM ]]
[[ BELOW IS WHAT THE VMWARE LABEL LOOKS LIKE ACCORDING TO
format(1M) "verify" subcommand -- it shows a sector size of "32".]]
==============================================================
Volume name = < >
ascii name = <DEFAULT cyl 4093 alt 2 hd 128 sec 32>
pcyl = 4095
ncyl = 4093
acyl = 2
bcyl = 0
nhead = 128
nsect = 32
Part Tag Flag Cylinders Size Blocks
0 unassigned wm 0 0 (0/0/0) 0
1 unassigned wm 0 0 (0/0/0) 0
2 backup wu 0 - 4092 7.99GB (4093/0/0) 16764928
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 - wu 0 - 4092 7.99GB (4093/0/0) 16764928
8 boot wu 0 - 0 2.00MB (1/0/0) 4096
9 unassigned wm 0 0 (0/0/0) 0
==============================================================
It might be possible to change VMDK disk emulation parameters within the
VMWARE configuration file (*.vmx), but how, and to what values? In other
words, what values would satisfy Volume manager. Or, along other lines, is there
a configuration parameter that can be implemented on the Volume Manager
side that will make the above disk settings acceptable to it.
BTW... I opened up a case with Veritas and am waiting for them to get back
to me.
Any ideas in the meantime; Thanks!
Noel Milton
This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
