resolving "Data Corruption Protection Activated"
Hello, recently I've noticed a number of servers giving the error below:
VxVM vxdisk ERROR V-5-1-14519 Data Corruption Protection Activated - User Corrective Action Needed
VxVM vxdisk INFO V-5-1-14521 To recover, first ensure that the OS device tree is up to date (requires OS specific commands).
VxVM vxdisk INFO V-5-1-14520 Then, execute 'vxdisk rm' on the following devices before reinitiating device discovery: <device list follows here...>
This occurs after discovering new EMC disk and following up with vxdisk scandisks, and it seems to stop me from scanning for new disks. I've followed usual steps of presenting and scanning for san disk, have never seen this issue before but now it's showing up on multiple servers.
Found this interesting forum discussion - "LUN Removal Process - Solaris 10 U8 / Storage Foundation 5.1 / PowerPath 5.3" and followed the steps for removing luns, thinking this might be the issue, but rescanning results in same error.
A reboot of a production server where I was having this problem did seem to fix it, but as I have about 8 other production boxes and as many development boxes it's not practical to try to reboot them all - big business impact.
Have tried researching quite a bit online, any ideas or help?
Hello,
to answer first part, yes thats quite possible, the warning is actually pointing to the same reason what you are guessing, you shouldn't accidently supress all the paths which may result in an outage.. To my belief (though I have not tried recently), vxvm will warn you befre supress however it won't care if that was the last surviving path....
to answer second part, /etc/vx/disk.info file use to contain the device mappings... this was there till 5.0 however 5.1 seems to have removed this file.. you can move this file while your applications are up, it won't have any impact... once you restart vxconfigd daemon, this file will be generated automatically..
moving disk.info is mostly recommended in device tree related issues for e.g, disk names not matching or not appearing as expected.... something changed after reboot ... or new luns not visible.. its common step for device tree cleanup which can be done online.
hope this answers..
Gaurav