Filter
Top Products
176 Creating and administering disk groups
Handling disks with duplicated identifiers
compared with the UDID that is set in the disk’s private region. If the UDID
values do not match, the udid_mismatch flag is set on the disk. This flag can be
viewed with the
vxdisk list command.
A new set of
vxdisk and vxdg operations are provided to handle such disks;
either by writing the DDL value of the UDID to a disk’s private region, or by
tagging a disk and specifying that it is a cloned disk to the
vxdg import
operation.
The following is sample output from the vxdisk list command showing that
disks c2t66d0, c2t67d0 and c2t68d0 are marked with the udid_mismatch
flag:
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t06d0 auto:cdsdisk - - online
c0t16d0 auto:cdsdisk - - online
...
c2t64d0 auto:cdsdisk - - online
c2t65d0 auto:cdsdisk - - online
c2t66d0 auto:cdsdisk - - online udid_mismatch
c2t67d0 auto:cdsdisk - - online udid_mismatch
c2t68d0 auto:cdsdisk - - online udid_mismatch
Writing a new UDID to a disk
You can use the following command to update the unique disk identifier (UDID)
for one or more disks:
# vxdisk [-f] [-g diskgroup] updateudid disk ...
This command uses the current value of the UDID that is stored in the Device
Discovery Layer (DDL) database to correct the value in the private region. The
-f
option must be specified if VxVM has not set the udid_mismatch flag for a
disk.
For example, the following command updates the UDIDs for the disks c2t66d0
and c2t67d0:
# vxdisk updateudid c2t66d0 c2t67d0
Importing a disk group containing cloned disks
By default, disks on which the udid_mismatch flag or the clone_disk flag
has been set are not imported by the
vxdg import command unless all disks in
the disk group have at least one of these flags set, and no two of the disks have
the same UDID. You can then import the cloned disks by specifying the
-o useclonedev=on option to the vxdg import command, as shown in this
example: