This page lists publically-released patches for Veritas Enterprise Products.
For Product GA build, see Veritas Entitlement Management System(VEMS) by clicking the Veritas Support 'Licensing' option.
For information on private patches, contact Veritas Technical Support.
Veritas is making it easier to find all software installers and updates for Veritas products with a completely redesigned experience. NetBackup HotFixes and NetBackup Appliance patches are now also available at the new Veritas Download Center.
Patches for your product can have a variety of names. These names are based on product, component, or package names. For more information on patch naming conventions and the relationship between products, components, and packages, see the SORT online help.
sfha-rhel6.6_x86_64-6.0.5.200
Sign in if you want to rate this patch.

 Basic information
Release type: Patch
Release date: 2014-12-18
OS update support: RHEL6 x86-64 Update 6
Technote: TECH164885: Late Breaking News (LBN), TECH225234: Issue, TECH226485: VxFS inotify issue
Documentation: None
Popularity: 4793 viewed    781 downloaded
Download size: 34.14 MB
Checksum: 1165053451

 Applies to one or more of the following products:
VirtualStore 6.0.1 On RHEL6 x86-64
Dynamic Multi-Pathing 6.0.1 On RHEL6 x86-64
Storage Foundation 6.0.1 On RHEL6 x86-64
Storage Foundation Cluster File System 6.0.1 On RHEL6 x86-64
Storage Foundation for Oracle RAC 6.0.1 On RHEL6 x86-64
Storage Foundation HA 6.0.1 On RHEL6 x86-64

 Obsolete patches, incompatibilities, superseded patches, or other requirements:

This patch supersedes the following patches: Release date
fs-rhel6_x86_64-6.0.5.200 (obsolete) 2014-12-18
sfha-rhel6.6_x86_64-6.0.5.100 (obsolete) 2014-11-21
fs-rhel6_x86_64-6.0.5.100 (obsolete) 2014-09-10

This patch requires: Release date
sfha-rhel6_x86_64-6.0.5 2014-04-15

 Fixes the following incidents:
2705336, 2853712, 2860207, 2863672, 2876865, 2892499, 2892590, 2892621, 2892643, 2892650, 2892660, 2892682, 2892684, 2892689, 2892698, 2892702, 2892716, 2912412, 2922798, 2924117, 2924188, 2924207, 2928921, 2933290, 2933291, 2933292, 2933294, 2933296, 2933309, 2933313, 2933330, 2933333, 2933335, 2933468, 2933469, 2933571, 2933729, 2933751, 2933822, 2934259, 2937367, 2940447, 2941193, 2941224, 2941226, 2941234, 2941237, 2941252, 2942166, 2942259, 2942336, 2944708, 2944710, 2944714, 2944717, 2944722, 2944724, 2944725, 2944727, 2944729, 2944741, 2960654, 2962257, 2965542, 2973659, 2974602, 2974870, 2976664, 2976946, 2978189, 2978227, 2978234, 2979767, 2982161, 2983679, 2983739, 2984589, 2987373, 2988017, 2988018, 2988749, 2999566, 2999881, 3004823, 3004852, 3005921, 3006262, 3008450, 3011391, 3011444, 3020087, 3022349, 3025973, 3026288, 3027250, 3027482, 3032358, 3033904, 3036949, 3043206, 3049356, 3056103, 3059000, 3089749, 3090670, 3094185, 3100385, 3108176, 3140411, 3144764, 3150893, 3156719, 3159096, 3189041, 3195695, 3197460, 3209160, 3210759, 3248029, 3248042, 3248046, 3248054, 3254132, 3254133, 3254199, 3254201, 3254204, 3254205, 3254227, 3254229, 3254231, 3254233, 3254301, 3254427, 3261607, 3264166, 3271596, 3271764, 3280555, 3283644, 3283668, 3294641, 3294642, 3296988, 3306164, 3309931, 3310758, 3312134, 3312311, 3317118, 3321337, 3338024, 3338026, 3338030, 3338063, 3338750, 3338762, 3338776, 3338779, 3338780, 3338781, 3338787, 3338790, 3339230, 3339884, 3339949, 3339963, 3339964, 3340029, 3340031, 3344127, 3344128, 3344129, 3344130, 3344132, 3344134, 3344138, 3344140, 3344142, 3344143, 3344145, 3344148, 3344150, 3344161, 3344167, 3344175, 3344264, 3344268, 3344286, 3347380, 3348459, 3349652, 3349877, 3349917, 3349937, 3349939, 3349985, 3349990, 3350000, 3350019, 3350027, 3350232, 3350235, 3350241, 3350265, 3350288, 3350293, 3350786, 3350787, 3350789, 3350979, 3350989, 3351005, 3351035, 3351075, 3351092, 3351125, 3351922, 3351939, 3351946, 3351947, 3352027, 3352208, 3352226, 3352282, 3352963, 3353059, 3353064, 3353131, 3353244, 3353291, 3353953, 3353985, 3353990, 3353995, 3353997, 3354023, 3354024, 3354028, 3355830, 3355856, 3355878, 3355883, 3355971, 3355973, 3356836, 3356841, 3356845, 3356892, 3356895, 3356909, 3357264, 3357278, 3358310, 3358313, 3358345, 3358346, 3358348, 3358351, 3358352, 3358354, 3358367, 3358368, 3358369, 3358370, 3358371, 3358372, 3358373, 3358374, 3358377, 3358379, 3358380, 3358381, 3358382, 3358404, 3358414, 3358416, 3358417, 3358418, 3358420, 3358423, 3358429, 3358433, 3359278, 3361977, 3361998, 3362062, 3362065, 3362087, 3362138, 3362144, 3362234, 3362923, 3362948, 3364285, 3364289, 3364302, 3364305, 3364307, 3364317, 3364333, 3364335, 3364338, 3364349, 3364353, 3364355, 3365295, 3365296, 3365313, 3365321, 3365390, 3366670, 3366688, 3366703, 3368236, 3368953, 3369037, 3369039, 3370650, 3371753, 3372896, 3372909, 3373213, 3374166, 3374735, 3375424, 3375575, 3377209, 3380905, 3381922, 3381928, 3383150, 3383271, 3384633, 3384636, 3384662, 3384697, 3384781, 3384986, 3386843, 3387376, 3387405, 3387417, 3387847, 3394692, 3395095, 3395499, 3396539, 3401836, 3402484, 3405172, 3405318, 3408321, 3409473, 3409692, 3411725, 3413044, 3414151, 3414265, 3416320, 3416406, 3417081, 3417672, 3420074, 3423613, 3423644, 3424795, 3426009, 3427124, 3427480, 3429328, 3429587, 3430687, 3434079, 3434080, 3434189, 3435000, 3435008, 3436393, 3461200, 3468413, 3469683, 3496715, 3498950, 3498954, 3498963, 3498976, 3498978, 3498998, 3499005, 3499008, 3499011, 3499014, 3499030, 3501358, 3502662, 3514824, 3515559, 3515569, 3515588, 3515737, 3515739, 3517702, 3517707, 3521727, 3526501, 3531332, 3552411, 3557193, 3567855, 3579957, 3581566, 3584297, 3588236, 3590573, 3595894, 3597454, 3597560, 3600161, 3612801, 3621240, 3622069, 3622423, 3632969, 3638039, 3665733, 3673958, 3678626

 Patch ID:
VRTSvxvm-6.0.500.100-RHEL6
VRTSvxfs-6.0.500.200-RHEL6
VRTSaslapm-6.0.500.300-GA_RHEL6

 Readme file  [Save As...]
                          * * * READ ME * * *
            * * * Veritas Storage Foundation HA 6.0.5 * * *
                      * * * Patch 6.0.5.200 * * *
                         Patch Date: 2014-12-18


This document provides the following information:

   * PATCH NAME
   * OPERATING SYSTEMS SUPPORTED BY THE PATCH
   * PACKAGES AFFECTED BY THE PATCH
   * BASE PRODUCT VERSIONS FOR THE PATCH
   * SUMMARY OF INCIDENTS FIXED BY THE PATCH
   * DETAILS OF INCIDENTS FIXED BY THE PATCH
   * INSTALLATION PRE-REQUISITES
   * INSTALLING THE PATCH
   * REMOVING THE PATCH
   * KNOWN ISSUES


PATCH NAME
----------
Veritas Storage Foundation HA 6.0.5 Patch 6.0.5.200


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
RHEL6 x86-64


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSaslapm
VRTSvxfs
VRTSvxvm


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Symantec VirtualStore 6.0.1
   * Veritas Dynamic Multi-Pathing 6.0.1
   * Veritas Storage Foundation 6.0.1
   * Veritas Storage Foundation Cluster File System HA 6.0.1
   * Veritas Storage Foundation for Oracle RAC 6.0.1
   * Veritas Storage Foundation HA 6.0.1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: VRTSvxfs-6.0.500.200
* 3622423 (3250239) Panic in vx_naio_worker
* 3673958 (3660422) On RHEL 6.6, umount(8) system call hangs if an application is watching for inode
events using inotify(7) APIs.
* 3678626 (3613048) Support vectored AIO on Linux
Patch ID: VRTSvxvm-6.0.500.100
* 3496715 (3281004) For DMP minimum queue I/O policy with large number of CPUs a couple of issues 
are observed.
* 3501358 (3399323) The reconfiguration of Dynamic Multipathing (DMP) database fails.
* 3502662 (3380481) When you select a removed disk during the "5 Replace a failed or removed disk" operation, the vxdiskadm(1M) command displays an error message.
* 3521727 (3521726) System panicked for double freeing IOHINT.
* 3526501 (3526500) Disk IO failures occur with DMP IO timeout error messages when DMP (Dynamic Multi-pathing) IO statistics demon is not running.
* 3531332 (3077582) A Veritas Volume Manager (VxVM) volume may become inaccessible causing the read/write operations to fail.
* 3552411 (3482026) The vxattachd(1M) daemon reattaches plexes of manually detached site.
* 3600161 (3599977) During replica connection, referencing a port which is already deleted in 
another thread caused system panic.
* 3612801 (3596330) 'vxsnap refresh' operation fails with `Transaction aborted waiting for IO 
drain` error
* 3621240 (3621232) vradmin ibc command cannot be started/executed on VVR (Veritas Volume 
Replicator) Secondary.
* 3622069 (3513392) Reference to replication port that is already deleted caused panic.
* 3632969 (3631230) VRTSvxvm patch version 6.0.5 and 6.1.1 or previous will not work with RHEL6.6
update.
* 3638039 (3625890) Vxdisk resize a CDS disk failing with "invalid attribute specification"
Patch ID: VRTSaslapm-6.0.500.300
* 3665733 (3665727) Array I/O POLICY is set to Single-active for SF6.1.1 with RHEL6.6

NOTE: For the incidents fixed in the previous patches please
refer to the product level readme files inside rpms folder.

DETAILS OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
This patch fixes the following Symantec incidents:

Patch ID: VRTSvxfs-6.0.500.200

* 3622423 (Tracking ID: 3250239)

SYMPTOM:
Panic in vx_naio_worker, trace back:-
crash_kexec()
__die ()
do_page_fault()
error_exit()
vx_naio_worker()
vx_kthread_init()
kernel_thread()

DESCRIPTION:
If a thread submitting linux native AIO has posix sibling threads, and it 
simply exits after the submit, then kernel will not wait for the aio to finish 
in the exit processing. When aio complete, it may dereference the task_struct 
of that exited thread, this cause the panic.

RESOLUTION:
Install vxfs hook to task_struct, so when the thread exits, it will wait for 
its aio to complete no matter it's cloned or not. Set module load-time tunable 
vx_naio_wait to non-zero value to turn on this fix.

* 3673958 (Tracking ID: 3660422)

SYMPTOM:
On RHEL 6.6, umount(8) system call hangs if an application is watching for inode
events using inotify(7) APIs.

DESCRIPTION:
On RHEL 6.6, additional counters were added in the super block to track inotify
watches, these new counters were not implemented in VxFS.
Hence while doing umount, the operation hangs until the counter in the
superblock drops to zero, which would never happen since they are not handled in
VXFS.

RESOLUTION:
Code is modified to handle additional counters added in RHEL6.6.

* 3678626 (Tracking ID: 3613048)

SYMPTOM:
System can panic with the following stack::
 
machine_kexec
crash_kexec
oops_end
die
do_invalid_op
invalid_op
aio_complete
vx_naio_worker
vx_kthread_init

DESCRIPTION:
VxFS does not correctly support IOCB_CMD_PREADV and IOCB_CMD_PREADV, which 
causes a BUG to fire in the kernel code (in fs/aio.c:__aio_put_req()).

RESOLUTION:
Add support for the vectored AIO commands and fixed the increment of ->ki_users 
so it is guarded by the required spinlock.

Patch ID: VRTSvxvm-6.0.500.100

* 3496715 (Tracking ID: 3281004)

SYMPTOM:
For DMP minimum queue I/O policy with large number of CPUs, the following 
issues are observed since the VxVM 5.1 SP1 release: 
1. CPU usage is high. 
2. I/O throughput is down if there are many concurrent I/Os.

DESCRIPTION:
The earlier minimum queue I/O policy is used to consider the host controller 
I/O load to select the least loaded path. For VxVM 5.1 SP1 version, an addition 
was made to consider the I/O load of the underlying paths of the selected host 
based controllers. However, this resulted in the performance issues, as there 
were lock contentions with the I/O processing functions and the DMP statistics 
daemon.

RESOLUTION:
The code is modified such that the host controller paths I/O load is not 
considered to avoid the lock contention.

* 3501358 (Tracking ID: 3399323)

SYMPTOM:
The reconfiguration of Dynamic Multipathing (DMP) database fails with the below error: VxVM vxconfigd DEBUG  V-5-1-0 dmp_do_reconfig: DMP_RECONFIGURE_DB failed: 2

DESCRIPTION:
As part of the DMP database reconfiguration process, controller information from DMP user-land database is not removed even though it is removed from DMP kernel database. This creates inconsistency between the user-land and kernel-land DMP database. Because of this, subsequent DMP reconfiguration fails with above error.

RESOLUTION:
The code changes have been made to properly remove the controller information from the user-land DMP database.

* 3502662 (Tracking ID: 3380481)

SYMPTOM:
When the vxdiskadm(1M) command selects a removed disk during the "5 Replace a failed or removed disk" operation, the vxdiskadm(1M) command displays the following error message:
"/usr/lib/vxvm/voladm.d/lib/vxadm_syslib.sh: line 2091:return: -1: invalid option".

DESCRIPTION:
From bash version 4.0, bash doesnt accept negative error values. If VxVM scripts return negative values to bash, the error message is displayed.

RESOLUTION:
The code is modified so that VxVM scripts dont return negative values to bash.

* 3521727 (Tracking ID: 3521726)

SYMPTOM:
When using Symantec Replication Option, system panic happens while freeing
memory with the following stack trace on AIX,

pvthread+011500 STACK:
[0001BF60]abend_trap+000000 ()
[000C9F78]xmfree+000098 ()
[04FC2120]vol_tbmemfree+0000B0 ()
[04FC2214]vol_memfreesio_start+00001C ()
[04FCEC64]voliod_iohandle+000050 ()
[04FCF080]voliod_loop+0002D0 ()
[04FC629C]vol_kernel_thread_init+000024 ()
[0025783C]threadentry+00005C ()

DESCRIPTION:
In certain scenarios, when a write IO gets throttled or un-winded in VVR, we
free the memory related to one of our data structures. When we restart this IO,
the same memory gets illegally accessed and freed again even though it was
freed.It causes system panic.

RESOLUTION:
Code changes have been done to fix the illegal memory access issue.

* 3526501 (Tracking ID: 3526500)

SYMPTOM:
Disk IO failures occur with DMP IO timeout error messages when DMP (Dynamic Multi-pathing) IO statistics daemon is not running. Following are the timeout error messages:

VxVM vxdmp V-5-3-0 I/O failed on path 65/0x40 after 1 retries for disk 201/0x70
VxVM vxdmp V-5-3-0 Reached DMP Threshold IO TimeOut (100 secs) I/O with start 
3e861909fa0 and end 3e86190a388 time
VxVM vxdmp V-5-0-0 [Error] i/o error occurred (errno=0x206) on dmpnode 201/0x70

DESCRIPTION:
When IO is submitted to DMP, it sets the start time on the IO buffer. The value of the start time depends on whether the DMP IO statistics daemon is running or not. When the IO is returned as error from SCSI to DMP, instead of retrying the IO on alternate paths, DMP failed that IO with 300 seconds timeout error, but the IO has elapsed only few milliseconds in its execution. The miscalculation of DMP timeout happens only when DMP IO statistics daemon is not running.

RESOLUTION:
The code is modified to calculate appropriate DMP IO timeout value when DMP IO statistics demon is not running.

* 3531332 (Tracking ID: 3077582)

SYMPTOM:
A Veritas Volume Manager (VxVM) volume may become inaccessible causing the read/write operations to fail with the following error:
# dd if=/dev/vx/dsk/<dg>/<volume> of=/dev/null count=10
dd read error: No such device
0+0 records in
0+0 records out

DESCRIPTION:
If I/Os to the disks timeout due to some hardware failures like weak Storage Area Network (SAN) cable link or Host Bus Adapter (HBA) failure, VxVM assumes that the disk is faulty or slow and it sets the failio flag on the disk. Due to this flag, all the subsequent I/Os fail with the No such device error.

RESOLUTION:
The code is modified such that vxdisk now provides a way to clear the failio flag. To check whether the failio flag is set on the disks, use the vxkprint(1M) utility (under /etc/vx/diag.d). To reset the failio flag, execute the vxdisk set <disk_name> failio=off command, or deport and import the disk group that holds these disks.

* 3552411 (Tracking ID: 3482026)

SYMPTOM:
The vxattachd(1M) daemon reattaches plexes of manually detached site.

DESCRIPTION:
The vxattachd daemon reattaches plexes for a manually detached site that is the site with state as OFFLINE. As there was no check to differentiate between a manually detach site and the site that was detached due to IO failure. Hence, the vxattachd(1M) daemon brings the plexes online for manually detached site also.

RESOLUTION:
The code is modified to differentiate between manually detached site and the site detached due to IO failure.

* 3600161 (Tracking ID: 3599977)

SYMPTOM:
system panics with following stack trace:
[00009514].simple_lock+000014
[004E4C48]soereceive+001AA8
[00504770]soreceive+000010
[00014F50].kernel_add_gate_cstack+000030
[04F6992C]kmsg_sys_rcv+000070
[04F89448]nmcom_get_next_mblk+0000A4
[04F63618]nmcom_get_next_msg+0000F0
[04F64434]nmcom_wait_msg_tcp+00015C
[04F7A71C]nmcom_server_proc_tcp+00006C
[04F7C7AC]nmcom_server_proc_enter+0000A4
[04D88AF4]vxvm_start_thread_enter+00005C

DESCRIPTION:
During replica connection, after created the port before increasing the count 
to protect the port from deleting, another thread deletes the port. While the 
replica connection thread proceeds, it refers to the port that is already 
deleted, hence causes NULL pointer reference and panic.

RESOLUTION:
Code changes have been done to add locking to the checking and modification of 
the count associated with the port.

* 3612801 (Tracking ID: 3596330)

SYMPTOM:
'vxsnap refresh' operation fails with following indicants:

Errors occur from DR (Disaster Recovery) Site of VVR (Veritas 
Volume Replicator):

o	vxio: [ID 160489 kern.notice] NOTICE: VxVM vxio V-5-3-1576 commit: 
Timedout waiting for rvg [RVG] to quiesce, iocount [PENDING_COUNT] msg 0
o	vxvm:vxconfigd: [ID 702911 daemon.warning] V-5-1-8011 Internal 
transaction failed: Transaction aborted waiting for io drain

At the same time, following errors occur from Primary Site of VVR:

vxio: [ID 218356 kern.warning] WARNING: VxVM VVR vxio V-5-0-267 Rlink 
[RLINK] disconnecting due to ack timeout on update message

DESCRIPTION:
VM (Volume Manager) Transactions on DR site get aborted as pending IOs could 
not be drained in stipulated time leading to failure of FMR (Fast-Mirror 
Resync) 'snap' operations. These IOs could not be drained because of IO 
throttling. A bug/race in conjunction with timing in VVR causes a miss in 
clearing this throttling condition/state.

RESOLUTION:
Code changes have been done to fix the race condition which ensures clearance 
of throttling state at appropriate time.

* 3621240 (Tracking ID: 3621232)

SYMPTOM:
When run IBC(In-band Control) procedure by vradmin ibc command, vradmind (VVR 
daemon) on VVR secondary may goes into disconnected state, then the following 
IBC procedure or vradmin ibc commands cannot be started/executed on VVR 
secondary and below message will be outputted on VVR primary.
    
VxVM VVR vradmin ERROR V-5-52-532 Secondary is undergoing a state transition. 
Please re-try the command after some time.
VxVM VVR vradmin ERROR V-5-52-802 Cannot start command execution on Secondary.

DESCRIPTION:
When IBC procedure run into command finish state, the vradmind on VVR secondary 
may goes into disconnected state, but it was not sensed by vradmind on primary. 
In such situation, the vradmind on primary will not send handshake request to 
the secondary which can take it out of disconnected state to running state. 
Then the vradmind will stall in disconnected state and the following vradmin 
ibc command cannot be executed on VVR secondary, although vradmind looks 
normal and in running state on VVR primary.

RESOLUTION:
Code changes have been done to make sure the vradmind on VVR primary will be 
notified while it goes into disconnected state on VVR secondary, hence it can 
send out handshake request to take the secondary out of disconnected state.

* 3622069 (Tracking ID: 3513392)

SYMPTOM:
secondary panics when rebooted while heavy IOs are going on primary

PID: 18862  TASK: ffff8810275ff500  CPU: 0   COMMAND: "vxiod"
#0 [ffff880ff3de3960] machine_kexec at ffffffff81035b7b
#1 [ffff880ff3de39c0] crash_kexec at ffffffff810c0db2
#2 [ffff880ff3de3a90] oops_end at ffffffff815111d0
#3 [ffff880ff3de3ac0] no_context at ffffffff81046bfb
#4 [ffff880ff3de3b10] __bad_area_nosemaphore at ffffffff81046e85
#5 [ffff880ff3de3b60] bad_area_nosemaphore at ffffffff81046f53
#6 [ffff880ff3de3b70] __do_page_fault at ffffffff810476b1
#7 [ffff880ff3de3c90] do_page_fault at ffffffff8151311e
#8 [ffff880ff3de3cc0] page_fault at ffffffff815104d5
#9 [ffff880ff3de3d78] volrp_sendsio_start at ffffffffa0af07e3 [vxio]
#10 [ffff880ff3de3e08] voliod_iohandle at ffffffffa09991be [vxio]
#11 [ffff880ff3de3e38] voliod_loop at ffffffffa0999419 [vxio]
#12 [ffff880ff3de3f48] kernel_thread at ffffffff8100c0ca

DESCRIPTION:
If the replication stage IOs are started after serialization of the replica volume, 
replication port  could be deleted  and set to NULL during handling the replica 
connection changes,  this will cause the panic since we have not checked if the 
replication port is still valid before referencing to it.

RESOLUTION:
Code changes have been done to abort the stage IO if replication port is NULL.

* 3632969 (Tracking ID: 3631230)

SYMPTOM:
VRTSvxvm patch version 6.0.5 and 6.1.1 will not work with RHEL6.6 update.

# rpm -ivh VRTSvxvm-6.1.1.000-GA_RHEL6.x86_64.rpm
Preparing...                ########################################### [100%]
   1:VRTSvxvm               ########################################### [100%]
Installing file /etc/init.d/vxvm-boot
creating VxVM device nodes under /dev
WARNING: No modules found for 2.6.32-494.el6.x86_64, using compatible modules 
for 
2.6.32-71.el6.x86_64. 
FATAL: Error inserting vxio (/lib/modules/2.6.32-
494.el6.x86_64/veritas/vxvm/vxio.ko): Unknown symbol in module, or unknown 
parameter 
(see dmesg) ERROR: modprobe error for vxio. See documentation.
warning: %post(VRTSvxvm-6.1.1.000-GA_RHEL6.x86_64) scriptlet failed, exit 
status 1

#

Or after OS update, the system log file will have the following messages logged.

vxio: disagrees about version of symbol poll_freewait
vxio: Unknown symbol poll_freewait
vxio: disagrees about version of symbol poll_initwait
vxio: Unknown symbol poll_initwait

DESCRIPTION:
Installation of VRTSvxvm patch version 6.0.5 and 6.1.1 fails on RHEL6.6 due to 
the changes in poll_initwait() and poll_freewait() interfaces.

RESOLUTION:
The VxVM package has re-compiled with RHEL6.6 build environment.

* 3638039 (Tracking ID: 3625890)

SYMPTOM:
Error message is reported as bellow after running vxdisk resize command:
"VxVM vxdisk ERROR V-5-1-8643 Device ibm_shark0_9: resize failed: Invalid 
attribute specification"

DESCRIPTION:
For CDS(cross platform data sharing) VTOC(volume table of contents) disks, 
there are 2 reserved cylinders for special usage. In case of expanding a disk 
with particular disk size on storage side, VxVM(veritas volume manager) may calculate the cylinder number as 2, which will cause the vxdisk 
resize failed with "Invalid attribute specification".

RESOLUTION:
Code changes have been made to avoid failure of resizing a CDS VTOC disk.

Patch ID: VRTSaslapm-6.0.500.300

* 3665733 (Tracking ID: 3665727)

SYMPTOM:
vxdmpadm listapm output does not list any APM except default ones

[root@rpms]# vxdmpadm listapm
Filename           APM Name           APM Version  Array Types       State
================================================================================
dmpjbod.ko         dmpjbod                1        Disk              Active
dmpjbod.ko         dmpjbod                1        APdisk            Active
dmpalua.ko         dmpalua                1        ALUA              Not-Active
dmpaaa.ko          dmpaaa                 1        A/A-A             Not-Active
dmpapg.ko          dmpapg                 1        A/PG              Not-Active
dmpapg.ko          dmpapg                 1        A/PG-C            Not-Active
dmpaa.ko           dmpaa                  1        A/A               Active
dmpap.ko           dmpap                  1        A/P               Active
dmpap.ko           dmpap                  1        A/P-C             Active
dmpapf.ko          dmpapf                 1        A/PF-VERITAS      Not-Active
dmpapf.ko          dmpapf                 1        A/PF-T3PLUS       Not-Active
[root@rpms]#

DESCRIPTION:
For supporting RHEL6.6 update, dmp module is recomipled with latest RHEL6.6 
kernel version. During post install of the package
the APM modules fails to load due to mismatch in DMP and additional APM module 
kernel version.

RESOLUTION:
ASLAPM package is recompiled with RHEL6.6 kernel.



INSTALLING THE PATCH
--------------------
Run the Installer script to automatically install the patch:
-----------------------------------------------------------
To install the patch perform the following steps on at least one node in the cluster:
1. Copy the patch sfha-rhel6.6_x86_64-6.0.5.200-rpms.tar.gz to /tmp
2. Untar sfha-rhel6.6_x86_64-6.0.5.200-rpms.tar.gz to /tmp/hf
    # mkdir /tmp/hf
    # cd /tmp/hf
    # gunzip /tmp/sfha-rhel6.6_x86_64-6.0.5.200-rpms.tar.gz
    # tar xf /tmp/sfha-rhel6.6_x86_64-6.0.5.200-rpms.tar
3. Install the hotfix
    # pwd 
    /tmp/hf
    # ./installSFHA605P2 [<host1> <host2>...]

You can also install this patch together with 6.0.1 GA release and 6.0.5 Patch release
    # ./installSFHA605P2 -base_path [<601 path>] -mr_path [<605 path>] [<host1> <host2>...]
where the -mr_path should point to the 6.0.5 image directory, while -base_path to the 6.0.1 image.

Install the patch manually:
--------------------------
o Before-the-upgrade :-
  (a) Stop I/Os to all the VxVM volumes.
  (b) Umount any filesystems with VxVM volumes.
  (c) Stop applications using any VxVM volumes.
o Select the appropriate RPMs for your system, and upgrade to the new patch.
   # rpm -Uhv VRTSvxvm-6.0.500.100-RHEL6.x86_64.rpm VRTSaslapm-6.0.500.300-GA_RHEL6.x86_64.rpm VRTSvxfs-6.0.500.200-RHEL6.x86_64.rpm


REMOVING THE PATCH
------------------
# rpm -e  <rpm-name>


KNOWN ISSUES
------------
* Tracking ID: 3688085

SYMPTOM: The 'delayed allocation' (ie 'dalloc') feature on VxFS 6.0.5.100
p-patch can cause data loss or stale data.

 Dalloc feature is enabled by default for local mounted file system
and is not supported for cluster mounted file systems. Dalloc with sequential
extending buffer writes can possibly cause data loss or stale data. This issue
is seen only with 6.0.5.100 p patch.

WORKAROUND: disable the 'delayed allocation' ('dalloc') feature on the VxFS filesystems.

Following commands are used to disable dalloc.

1)For a filesystem which is already mounted
# vxtunefs -s -o dalloc_enable=0 $MOUNT_POINT

2) To make the value persistent across system reboot, add an entry to
/etc/vx/tunefstab
/dev/vx/dsk/$DISKGROUP/$VOLUME      dalloc_enable=0



SPECIAL INSTRUCTIONS
--------------------
NONE


OTHERS
------
NONE



Read and accept Terms of Service