17.08.2015 Views

Veritas Storage Foundation and High Availability Solutions Release Notes

Veritas Storage Foundation™ and High ... - SORT - Symantec

Veritas Storage Foundation™ and High ... - SORT - Symantec

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

About <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong>Known issues63After devices that are managed by EMC PowerPath lose access to storage,<strong>Veritas</strong> Volume Manager comm<strong>and</strong>s are delayed (2757198)In an enviroment which includes devices that are managed by EMC PowerPath,a storage loss causes <strong>Veritas</strong> Volume Manager comm<strong>and</strong>s to be delayed. In theevent of storage loss, VxVM sends SCSI inquiry from each LUN path to check thehealth of path, which are delayed by the presence of EMC PowerPath.Complete site is detached, if plex detach operation is performed even aftersite consistency off (2845383)By design, you cannot detach the last plex of a site on a site consistent volumewithout detaching the complete site. By default, attempting to detach the last plexcauses an error. If you use the force detach option, then the complete site isdetached to ensure site consistency. This behavior is seen even if you turn off thesite consistent flag if the allsites flag is on.Performance impact when a large number of disks are reconnected(2802698)If the storage connectivity is lost to part of the storage, the disk groupconfiguration copy is rebalanced to the disks that have connectivity. For example,if the storage for an entire enclosure is removed from a disk group with mulipleenclosures. The rebalancing process takes time, during which time the vxconfigddaemon is busy <strong>and</strong> does not respond to comm<strong>and</strong>s.Plex synchronization is not completed after resuming synchronization ona new master when the original master lost connectivity (2788077)When you run vxrecover -o force, it recovers only one subvolume <strong>and</strong> it cannotdetect that the rest of the volume needs recovery.When you run the vxassist mirror comm<strong>and</strong>, you run the vxplex attcomm<strong>and</strong>serially on each subvolume. If the failure happens before you start theattachoperation (need to mark the concerned plex as the attach operation is inprogress), vxrecover will not redo the attach operation because it cannot findany record of the attach operation in progress.Workaround:Run the following comm<strong>and</strong> on each subvolume to manually recover the completevolume:# /usr/lib/vxvm/type/fsgen/vxplex -U fsgen -g diskgroup \-o force useopt att volume plex

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!