VxVM vxdg ERROR V-5-1-0 Disk Group oradg has only cloned disks

Issue

Unable to add a new disk to an existing diskgroup (DG) after upgrade to Veritas Volume Manager (VxVM) 5.1SP1RP3.

Error

# /usr/sbin/vxdg -g oradg adddisk 002oradg=emc2_0fe5
VxVM vxdg ERROR V-5-1-0 Disk Group oradg has only cloned disks and tyring to add standard disk to diskgroup. Mix of standard and cloned disks in a diskgroup is not allowed. Please follow the vxdg (1M) man page.


Environment

Solaris 10

VxVM 5.1SP1RP3

Cause

Prior to VxVM 5.1SP1RP3, vxdg adddisk command did not check whether the newly added disk is a clone or standard disk. 5.1SP1RP3 patch which introduced this check via e2815517 (vxdg adddisk should not allow mixing clone & non-clone disks in a DiskGroup) prevents mix of standard and clone disks in a DG.


Solution

If there is a mismatch of udid and udid_asl fields and/or clone_disk flag is set as seen in vxdisk -v list <disk> outputs, vxdisk updateudid needs to be run on the existing disks in the DG. This is explained in TECH196717.

 *** Error when adding disk to DG:
# /usr/sbin/vxdg -g oradg adddisk 002oradg=emc2_0fe5
VxVM vxdg ERROR V-5-1-0 Disk Group oradg has only cloned disks and tyring to add standard disk to diskgroup. Mix of standard and cloned disks in a diskgroup is not allowed. Please follow the vxdg (1M) man page.


*** Only 2 disks in DG:

# grep oradg vxdisk_alldg_list
emc1_151f    auto:cdsdisk    001oradg  oradg   online
emc1_0511    auto:cdsdisk    000oradg  oradg   online


*** Both disks have mismatched udid which means that vxvm considers the disks as clone disks.

# grep udid vxdisk_list_emc1_151f
udid:      EMC%5FSYMMETRIX%5F000290104663%5F630151F008
tag      udid_asl=EMC%5FSYMMETRIX%5F104663%5F6351F008

# grep udid vxdisk_list_emc1_0511
udid:      EMC%5FSYMMETRIX%5F000290104663%5F6300511000
tag      udid_asl=EMC%5FSYMMETRIX%5F104663%5F63511000


*** Whereas the new disk has matching udid, which means it is considered as standard disk.

# grep udid vxdisk_list_emc2_0fe5
udid:      EMC%5FSYMMETRIX%5F000292600663%5F6300FE5000
tag      udid_asl=EMC%5FSYMMETRIX%5F000292600663%5F6300FE5000

*** Procedure documented in TECH196717 needs to be run to fix the issue.

http://www.symantec.com/business/support/index?page=content&id=TECH196717

# vxdg deport oradg
# vxdisk -f updateudid emc1_151f
# vxdisk -f updateudid emc1_0511
# vxdisk set emc1_151f clone=off
# vxdisk set emc1_0511 clone=off
# vxdg import oradg
#

*** Once the udid is fixed, you would be able to add the new disk to the DG:

# vxdg -g oradg adddisk 002oradg=emc2_0fe5
#

Comments

Post a Comment

Popular posts from this blog

BMCs and the IPMI Protocol

Image
Baseboard Management Controllers (BMCs) are a type of embedded computer used to provide out-of-band monitoring for desktops and servers. These products are sold under many brand names, including HP iLO, Dell DRAC, Sun ILOM, Fujitsu iRMC, IBM IMM, and Supermicro IPMI. BMCs are often implemented as embedded ARM systems, running Linux and connected directly to the southbridge of the host system's motherboard. Network access is obtained either via 'sideband' access to an existing network card or through a dedicated interface. In addition to being built-in to various motherboards, BMCs are also sold as pluggable modules and PCI cards. Nearly all servers and workstations ship with or support some form of BMC. The Intelligent Platform Management Interface (IPMI) is a collection of specifications that define communication protocols for talking both across a local bus as well as the network. This specification is managed by Intel and currently comes in two flavors, ve...
Read more

Logical Domains Reference Manual

Image
Name ldm– command-line interface for the Logical Domains Manager Synopsis ldm or ldm --help [ subcommand ] ldm -V ldm add-domain -i file ldm add-domain [mac-addr= num ] [hostid= num ] [failure-policy=ignore|panic|reset|stop] [master= master-ldom1 ,..., master-ldom4 ] ldom ldm add-domain ldom ... ldm set-domain -i file ldm set-domain [failure-policy=ignore|panic|reset|stop] [master=[ master-ldom1 ,..., master-ldom4 ]] ldom ldm remove-domain -a ldm remove-domain ldom ... ldm list-domain [-e] [-l] [-o format ] [-p] [ ldom ...] ldm migrate-domain [-n] source-ldom [ user @] target-host [: target-ldom ] ldm add-vcpu number ldom ldm set-vcpu number ldom ldm remove-vcpu number ldom ldm add-crypto number ldom ldm set-crypto number ldom ldm remove-crypto number ldom ldm add-memory size [ unit ] ldom ldm set-memory size [ unit ] ldom ldm remove-memory size [ unit ] ldom ldm cancel-operation (migration | reconf) ldom ldm add-io [bypass=on] bus ...
Read more

Understanding How ZFS Calculates Used Space

This document explains how ZFS calculates the amount of used space within a zpool and provides examples of how various ZFS features affect that calculation. DETAILS A ZFS storage pool is a logical collection of devices that provide space for datasets such as filesystems, snapshots and volumes. A zfs pool can be used as a filesystem, i.e. such as mounting/unmounting; to take snapshots that provides read-only (clones are writable copies of snapshots) copies of the filesystem taken in the past; to create volumes that can be accessed as a raw and a block device and for setting properties on datasets. Interaction of all these datasets and associated properties such as quotas, reservations, compression and deduplication (Solaris 11 only) play a role in how ZFS calculates space usage. Neither the du nor df command have been updated to account for ZFS file system space usage. When calculating zfs space usage, always use the following command. # zfs list -r -o space <pool_name...
Read more