VxVM vxdg ERROR V-5-1-10978 Disk group : import failed: Disk group has no valid configuration copies

Issue

Diskgroups  will experience intermittent import failures if they contain a mix of standard and cloned devices in the (same) diskgroup

Error

VxVM vxdg ERROR V-5-1-10978 Disk group <diskgroupname>: import failed:
Disk group has no valid configuration copies

Sep  9 08:40:31 hostname vxvm:vxconfigd: [ID 702911 daemon.warning] V-5-1-0 Disk Group <diskgroupname> has a mix of standard and cloned disks: Trying to import the disk group from the standard disks: c3t5006048C52A83528d86s2 c3t5006048C52A83528d87s2

Environment

Storage Foundation Upgrade from : 5.0.x to 5.1.x and 6.0.x

PLATFORM(S):  SOLARIS, HPUX, AIX & LINUX

Cause

Volume Manager can cause intermittent diskgroup import failures for a diskgroup that has a mix of standard and cloned devices .

- Volume Manager implemented a change in version 5.1  that caused the Lun Serial Number (LSN)  for EMC arrays to be shorter than in previous versions.

-The UDID is a tuple( 4 field) consisting of : VendorId , Product ID, Cabinet Serial number , LSN.

- LSN format change from version 5.0.x to 5.1 leads to UDID mismatch upon upgrade for disks that were initialized in 5.0.x

-UDID mismatch triggers  the clone flag to be set internally and the diskgroup will be flagged/imported as “cloned”.

-If a disk is added to such a diskgroup it will be added as a STANDARD device causing the diskgroup to contain a mix of clone and standard devices.

Solution

For all the disks that have two different udid’s

i. If the disks are part of imported DG, deport the DG
 #vxdg deport dgname
ii. Clear the udid_mismatch flags on the disk using
  # vxdisk [-f] [-g diskgroup] updateudid disk ... ( use the –f option to forcibly update the UDID value if the update_udid flag is not set )
iii. Clear the clone flag on non-clone disks if set
#vxdisk set diskname clone=off
iv. Import the diskgroup if it was previously deported
#vxdg import dgname


 



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