Error Code details
V-5-1-14519
Severity: Critical 
Component: Volume Manager 
Message:
Data Corruption Protection Activated - User Corrective Action Needed
Description:

Data correction has not occurred, however, taking a subsequent incorrect action can result in data corruption. 

This message appears after a Veritas Volume Manager (VxVM) device scan if DMP detects an inconsistency in the DMP in-memory database and the physical devices. This type of inconsistency can occur if the storage administrator has:

  • Remapped previously used LUNS on a new host target ID
  • Mapped new LUNS on target IDs previously used by these remapped LUNs

This message is followed by messages similar to the following:

VxVM vxdctl INFO V-5-1-0  To recover, first ensure that the OS device tree is up
to date (requires OS specific commands).

VxVM vxdctl INFO V-5-1-0  Then, execute 'vxdisk rm' on the following devices
before reinitiating device discovery

 

Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2009-12-01 20:50:21 PST
Platform: Generic
Release: Generic
Content:

To resolve the inconsistency, perform the following device tree clean-up procedure.

This procedure should be performed by an experienced systems/storage administrator  with  advanced operating system skills and an understanding of storage mapping to the host.

To clean up the device tree:

  1. From the storage array management GUI or command line, unmap the LUNs that you mapped in the previous operation (before you ran vxdctl enable).
     
  2. Remove the entries for these LUNs from VxVM by entering the following command:

    # vxdisk rm da_name
     
  3. Clean up the operating system device tree. The operating system commands vary, depending on the operating system and version.

    The following steps use Solaris 10 with the Leadville stack. If any of these steps do not produce the desired result, contact Sun support. For the steps for Linux or AIX, see the section "Cleaning up the operating system device tree after removing LUNs" in the Veritas Volume Manager Administrator's Guide for Linux or AIX.

    a.    Run the format command. In the command output, a device that has been removed includes the text <drive not available>. For example:

         413. c3t5006048ACAFE4A7Cd252 <drive not available>
         /pci@1d,700000/SUNW,qlc@1,1/fp@0,0/ssd@w5006048acafe4a7c,fc

    b.    Use the storage array management GUI or the command line to unmap the LUNs. After you have unmapped them, Solaris indicates that the devices are either unusable or failing.

         #  cfgadm -al -o show_SCSI_LUN | grep -I unusable
         c2::5006048acafe4a73,256 disk connected configured unusable
         c3::5006048acafe4a7c,255 disk connected configured unusable

         # cfgadm -al -o show_SCSI_LUN | grep -I failing
         c2::5006048acafe4a73,71 disk connected configured failing
         c3::5006048acafe4a7c,252 disk connected configured failing

    c.    If the output indicates that the LUNs are failing, you must force an LIP on the HBA by entering the following command:

         # luxadm -e forcelip /devices/pci@1d,700000/SUNW,qlc@1,1/fp@0,0:devctl

    This operation probes the targets again, so that output indicates the devices are unstable. To remove a device from the operating system device tree, it must be unstable.

    d.    Remove the device from the cfgadm database. On the HBA, enter the following commands:

         # cfgadm -c unconfigure -o unusable_SCSI_LUN c2::5006048acafe4a73
         # cfgadm -c unconfigure -o unusable_SCSI_LUN c3::5006048acafe4a7c

    e.    To verify that the LUNs have been removed, repeat step b.

    f.    Clean up the device tree by entering the following command to remove the /dev/dsk links to /devices.

         # devfsadm -Cv

  4. Scan the operating system device tree. The operating system commands vary, depending on the operating system.

    The following steps use Solaris 10 with the Leadville stack. For the steps for Linux or AIX, see the section "Scanning an operating system device tree after adding or removing LUNs" in the Veritas Volume Manager Administrator's Guide for Linux or AIX.

    a. Enter the following command:
        
         # cfgadm -c configure c2

         where c2 is the controller ID 2.

    b. Enter the following command:

         # devfsadm -Cv
     
  5. From the storage array management GUI or command line, map the LUNs (that you unmapped in step 1) back.
     
  6. Scan the operating system device tree.
     
  7. Run the VxVM device scan again by entering the following command and verify that you no longer get the above error:

    # vxdisk scandisks

    If you still get the error, repeat this procedure until all duplicate device entries are removed.

 

User solutions
No user solutions yet.

 

Read and accept Terms of Service