
PROBLEM: (QAR.82428) (PATCH ID: TCR510-005)
********
The Quorum disk becomes inaccessible if manually adding Quorum disk by the
command "clu_quorum -d add" because the PR flag is not cleaned up. However;
it will work in the next reboot.
A member cannot boot under specific hardware due to the CFS mount fails 
because of the PR flag is not cleaned up.


PROBLEM: (84515, 84489, 83411, 83297,
          83658) (PATCH ID: TCR510-021)
********
This patch fixes several problems, including addressing the
need for IOCTL for remote DRD, adding clean up for 
failed remote closes for non-disks, fixing error returns on
failed tape/changer closes and fixes to tape deadlock experienced
in netbackups.


PROBLEM: (83065) (PATCH ID: TCR510-009)
********
This patch fixes an issue with a tape/changer failing
to correctly report a close failure of a device
in a cluster environment.


PROBLEM: (83038, N/A) (PATCH ID: TCR510-016)
********
This patch addresses two issues:
     - A problem which results in a system panic while doing tape failovers.
     - A node panic during fiber port disables.


PROBLEM: (83370) (PATCH ID: TCR510-011)
********
This patch fixes an issue with a tape/changer giving back busy on open if
a close from a remote node failed.


PROBLEM: (82423) (PATCH ID: TCR510-022)
********
This patch provides TCR portion of the functionality to support EMC storage 
boxes that support Persistent Reserves  (SCSI command set) as defined by 
the final SCSI specification.


PROBLEM: (83297) (PATCH ID: TCR510-012)
********
This patch fixes an issue with requests being stuck on a failed disk in a 
cluster


PROBLEM: (85547) (PATCH ID: TCR510-035)
********
This patch allows high density tape drives to use the high density
compression setting in a cluster environment.
While open a tape density file tape_d*, DRD driver would issue a special 
ioctl by using dev_t of tape0 (the default density file), this caused the 
device driver register all tape_d* with standand density, consequently,
no matter what density is specified, they all end up with the standard 
mode. The fix in DRD driver picks the correct dev_t.


PROBLEM: (87582) (PATCH ID: TCR510-038)
********
During the cluster failover time, if the cluster has any shared served
disk such as shared CD-ROM, the cluster members that directly connect
to the devive can crash with the message similiar to,
trap: invalid memory ifetch access from kernel mode

    faulting virtual address:     0x0000000000000000
    pc of faulting instruction:   0x0000000000000000
    ra contents at time of fault: 0xffffffff0052afd0
    sp contents at time of fault: 0xfffffe068993f820

panic (cpu 1): kernel memory fault


PROBLEM: (85944) (PATCH ID: TCR510-030)
********
This patch fixes an issue with the hwmgr -delete command that causes
a panic in a cluster. The panic string will look like this:
panic (cpu 5): kernel memory fault


PROBLEM: (86716:) (PATCH ID: TCR510-034)
********
This patch fixes the KZPCC DORADO controller problem seen when 
deleting a Virtual Drive using SWCC and adding the same drive 
back can result in the disk being unaccessable.


PROBLEM: (DE_G02949, DE_G02339, 91286, 81930,
          82822, 83156, 82727, 83522, 84489,
          86224, 87034, 87153, 87387, 88059,
          89405, 87101) (PATCH ID: TCR510-109)
********
This patch fixes several problems with the device request dispatcher (drd)
kernel subsystem, including: cluster hangs, kernel memory faults, reboot
problems, node recovery problems, and device failover problems.


PROBLEM: (90366, 91135) (PATCH ID: TCR510-108)
********
This patch fixes cluster hangs and panics due to I/O problems seen by customers
in stress testing.


PROBLEM: (90599) (PATCH ID: TCR510-094)
********
This patch fixes a problem where the tape changer is only accessible
from member that's the drd server for the changer.


PROBLEM: (90257) (PATCH ID: TCR510-065)
********
The ClusterIO (or DRD) will keep track of failed unbarrierable devices such
as CD-ROM or floppy disks by scanning the accessiblity periodically. If
there are multiple devices failed at the same time, there is a small 
window that can cause the cluster member crash because of "Same active 
event happened twice!" assert. This patch fixes this problem.


PROBLEM: (90961) (PATCH ID: TCR510-084)
********
Resources like tape/changers handled by CAA do not come online (according to
 CAA). The caa_stat command will return something like even though there is no\
 problem accessing the device:
NAME=tapeone
 TYPE=tape
 TARGET=ONLINE on hamm
 TARGET=ONLINE on woody
 STATE=OFFLINE on hamm
 STATE=OFFLINE on woody


PROBLEM: (TPOQ57031) (PATCH ID: TCR510-105)
********
This patch fixes a kernel memory fault in drd_open


PROBLEM: (89245, 90061, 90685, 90503,
          91148, 85235, BCGMC175K, ACXIOM536, DE_G02949,
          ACXIOM537, BCGMB26SC, BCGMA27CZ) (PATCH ID: TCR510-106)
********
This patch fixes the following problems:
- prevents HSG80 controller crashes.
- fixes cam_logger error message problems during cluster boot.
- fixes DRD problems and persistent reservation problems.
- fixes problems with drdmgr not responding to a failover disk.


PROBLEM: (84824) (PATCH ID: TCR510-090)
********
This patch fixes a problem whereby failover will not occur properly.


PROBLEM: (90755) (PATCH ID: TCR510-115)
********
This patch fixes a domain panic in a cluster when a file system is mounted
on a disk accessed remotely over the cluster interconnect.



