Veritas Storage Foundation Release Notes

Veritas Storage Foundation™ Release Notes: HP-UX - Symantec Veritas Storage Foundation™ Release Notes: HP-UX - Symantec

d1mj3xqaoh14j0.cloudfront.net
from d1mj3xqaoh14j0.cloudfront.net More from this publisher
17.08.2015 Views

36 Storage Foundation Release Notes Fixed issues Table 1-8 Incident 2425259 2421067 2419803 2419486 2419348 2413904 2411698 2410845 2407699 2407192 2406292 2400654 2396293 2390431 2389554 2388725 2387993 2386120 Veritas Volume Manager fixed issues (continued) Description vxdg join fails with VE_DDL_PROPERTY: Property not found in the list. vxconfigd hung in both nodes of primary. Pinnacle secondary master panics at nmcom_send_tcp during autosync. Data corruption when changing naming scheme. DMP panic; race condition between DMP reconfig and DMP pass through ioctl. Multiple issues are seen while performing dynamic LUN reconfiguration. I/O hangs on both master and slave. Lots of 'reservation conflict' messages seen in clustered environment with XIV arrays. vxassist core dump if the /etc/default/vxassist file contains wantmirror=ctlr. Application I/O hangs because of a race condition between CVM reconfiguration and log-owner change protocol. Panic in vol_subdisksio_delete. Stale array.info file can cause vxdmpadm commands to hang. I/Os loaded, sanboot failed with a vxconfigd core dump. VVR vxio panic at the end of autosync, when transitioning from DCM to SRL logging mode. vxdg listssbinfo output is not correct. Panic in dmp_get_dmpsymbols when attempting to load an APM. Including/excluding libvxpp.so vxconfigd goes into disabled mode. Enhancement request to add diagnostic logging to help triage a CVM master takeover failure situation.

Storage Foundation Release Notes Fixed issues 37 Table 1-8 Incident 2379029 2367564 2365951 2364868 2364253 2359814 2357798 2357507 2356744 2356293 2349352 2346470 2344186 2337353 2337233 2334757 Veritas Volume Manager fixed issues (continued) Description Changing of enclosure name is not working for all devices in enclosure. Long boot times observed due to vxvm-udev.sh since upgrading to 5.1SP1. Growto failing with error V-5-1-10128 Unexpected kernel error in configuration update. VxVM 5.0.1 will not upgrade in a DRD environment. VVR: Kernel memory is leaked on VVR secondary while using SO snapshots. vxconfigbackup doesn't handle errors well. CVR:Memory leak due to unfreed vol_ru_update structure. In presence of large number of NR (Not-Ready) devices, server panics due to NMI triggered and when DMP continuously generates large no of path disable/enable events. VxVM script daemons should not allow its duplication instance in itself. Hung in the DMP stack vxdmpread -> uphysio. During LUN provisioning in single path IO mode environment a data corruption is observed. Excluding and including a LUN in a loop triggers a huge memory leak. CCT: Volume recovery is not clearing the needsync flag from volumes with DCO in BADLOG state causing node join to fail. vxdmpadm include vxvm dmpnodename= includes all excluded dmpnodes along with the requested one. vxdmpadm exclude vxvm dmpnodename= does not suppress TPD device. memory consumption for the vxconfigd grows because of a lot of DMP_IDLE, DMP_UNIDLE events.

<strong>Storage</strong> <strong>Foundation</strong> <strong>Release</strong> <strong>Notes</strong><br />

Fixed issues<br />

37<br />

Table 1-8<br />

Incident<br />

2379029<br />

2367564<br />

2365951<br />

2364868<br />

2364253<br />

2359814<br />

2357798<br />

2357507<br />

2356744<br />

2356293<br />

2349352<br />

2346470<br />

2344186<br />

2337353<br />

2337233<br />

2334757<br />

<strong>Veritas</strong> Volume Manager fixed issues (continued)<br />

Description<br />

Changing of enclosure name is not working for all devices<br />

in enclosure.<br />

Long boot times observed due to vxvm-udev.sh since<br />

upgrading to 5.1SP1.<br />

Growto failing with error V-5-1-10128 Unexpected kernel<br />

error in configuration update.<br />

VxVM 5.0.1 will not upgrade in a DRD environment.<br />

VVR: Kernel memory is leaked on VVR secondary while<br />

using SO snapshots.<br />

vxconfigbackup doesn't handle errors well.<br />

CVR:Memory leak due to unfreed vol_ru_update structure.<br />

In presence of large number of NR (Not-Ready) devices,<br />

server panics due to NMI triggered and when DMP<br />

continuously generates large no of path disable/enable<br />

events.<br />

VxVM script daemons should not allow its duplication<br />

instance in itself.<br />

Hung in the DMP stack vxdmpread -> uphysio.<br />

During LUN provisioning in single path IO mode<br />

environment a data corruption is observed.<br />

Excluding and including a LUN in a loop triggers a huge<br />

memory leak.<br />

CCT: Volume recovery is not clearing the needsync flag from<br />

volumes with DCO in BADLOG state causing node join to<br />

fail.<br />

vxdmpadm include vxvm dmpnodename=<br />

includes all excluded dmpnodes along with the requested<br />

one.<br />

vxdmpadm exclude vxvm dmpnodename=<br />

does not suppress TPD device.<br />

memory consumption for the vxconfigd grows because of<br />

a lot of DMP_IDLE, DMP_UNIDLE events.

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

Saved successfully!

Ooh no, something went wrong!