Lun addition followed by a "vxdctl enable" operation can cause data corruption, when Volume Manager's (VxVM) configuration daemon, vxconfigd, is migrating disk-access names (DANAME) with simultaneous active I/O on the devices
|Article:TECH158119|||||Created: 2011-04-14|||||Updated: 2012-05-24|||||Article URL http://www.symantec.com/docs/TECH158119|
Data corruption can occur in any one of the following configurations, when new LUNs are provisioned or removed under VxVM, while IOs are in progress.
The following "WARNING" messages can be seen
vxio: [ID 914260 kern.notice] NOTICE: VxVM vxio V-5-0-1046 changing UDID for disk <DANAME>
vxio: [ID 718197 kern.notice] NOTICE: VxVM vxio V-5-0-1056 change disk <DANAME> has a non-unique UDID
There is a possibility of change in name of the DA records, when LUNs are removed or added followed by the following commands, since the persistence naming is OFF.
Set disk to persistence naming this problematic vxvm code can be avoided.
NOTE: PLEASE MAKE SURE ALL I/O's TO VOLUMES ARE STOPPED. FILE SYSTEMS MUST BE UNMOUNTED TO ENSURE THE PROBLEMATIC CODE IS AVOIDED.
- 5.0MP4RP1HF7 on Linux
During LUN provisioning in single path IO mode environment a data corruption is observed
Article URL http://www.symantec.com/docs/TECH158119