|
.___.___.___.___.___.___.___.
! ! ! ! ! ! ! !
! d ! i ! g ! i ! t ! a ! l ! I N T E R O F F I C E M E M O
!___!___!___!___!___!___!___!
TO: OpenVMS Software Group
DATE: 15-Jan-1997
FROM: Tom Collins
DEPT: QTV Group
EXT: 381-1329
LOC: ZK03-4S02
ENET: VMSSPT::COLLINS
SUBJECT: OpenVMS CLD Causal Analysis Report (Oct 1,1996 to Dec 31, 1996)
This report is an evaluation of the severity 1 and 2 IPMT Cases logged to
OpenVMS Sustaining Engineering during the 12 week period from Oct 1, 1996
to Dec 31, 1996. The purpose of this report is to identify the OpenVMS
software component areas where our installed base of customers are
encountering the highest amount of serious problems.
Overview: (Alpha)
During this 12 week period, 78 severity 1 and 2 IPMT problem reports were
logged against components of the Alpha Operating System.
6 were logged on Alpha V6.1, 37 on V6.2, 10 on V6.2-1H2, 18 on V6.2-1H3
and 7 on V7.0.
Overview: (VAX)
On VAX, 62 severity 1 and 2 problem reports were logged during this period.
3 Cases were logged on V5.5-2, 1 on V5.5-2H4, 23 on V6.1, 33 on V6.2, and
2 on V7.0.
The Case breakdown per component area was the following;
--------------------------------------------------------------------------------
Component Areas VAX Cases Logged Alpha Cases logged
--------------------------------------------------------------------------------
Backup 2 0
--------------------------------------------------------------------------------
Clusters
Cluster_srvr 2 0
Cnx_man 2 2
Lck_man 0 2
Mscp 1 1
Shadowing 3 3
Tmscp 1 1
VCC 1 1
--------------------------------------------------------------------------------
Configure 0 0
--------------------------------------------------------------------------------
DCE 3 1
--------------------------------------------------------------------------------
DECAMDS 1 0
--------------------------------------------------------------------------------
DECDFS 1 0
--------------------------------------------------------------------------------
DECDTM 0 5 (2 duplicates)
--------------------------------------------------------------------------------
DOSD 1 0
--------------------------------------------------------------------------------
Drivers
CTdriver 0 2
Drdriver 0 1
Dudriver 2 1
Lrdriver 0 1
Pndriver 0 4
Sodriver 0 2
--------------------------------------------------------------------------------
Errfmt 1 0
--------------------------------------------------------------------------------
Exception 0 0
--------------------------------------------------------------------------------
F11BXQP 7 (3 duplicates) 2
--------------------------------------------------------------------------------
Image_man 0 1
--------------------------------------------------------------------------------
Infoserver 4 (1 duplicate) 2
--------------------------------------------------------------------------------
Job Controller 0 0
--------------------------------------------------------------------------------
JVMS 0 3
--------------------------------------------------------------------------------
Lan
Esdriver 0 0
Etdriver 1 0
Ewdriver 0 3 (1 duplicate)
Exdriver 3 (1 duplicate) 0
Ezdriver 1 0
Fqdriver 1 0
Frdriver 0 0
Fwdriver 0 1
Fxdriver 2 0
Lanacp 0 1
Net$fddi 0 3
Xqdriver 0 1
--------------------------------------------------------------------------------
Lat
Ltdriver 1 0
Latacp 0 1
Latsym 0 1
TSM 0 1
--------------------------------------------------------------------------------
Linker 1 0
--------------------------------------------------------------------------------
Macro32 0 1
--------------------------------------------------------------------------------
Memory_man 2 2
--------------------------------------------------------------------------------
Mount/Dsmnt 0 1
--------------------------------------------------------------------------------
Page_man 1 0
--------------------------------------------------------------------------------
PCSI 0 1
--------------------------------------------------------------------------------
Posix 0 1
--------------------------------------------------------------------------------
Process_man 0 0
--------------------------------------------------------------------------------
Prtsym 0 0
--------------------------------------------------------------------------------
Queue_man 1 0
--------------------------------------------------------------------------------
RMS 0 1
--------------------------------------------------------------------------------
SCSI drivers
Dkdriver 0 2
Mkdriver 0 0
Pkbdriver 2 0
Pkcdriver 0 0
Pkedriver 0 0
Pkqdriver 0 1
Pksdriver 0 5 (1 duplicate)
Pktdriver 0 0
Pkzdriver 0 1
--------------------------------------------------------------------------------
Sda 1 0
--------------------------------------------------------------------------------
Security
Audit_srvr 0 2
Loginout 2 2
Opcom 1 0
Security_svr 2 0
--------------------------------------------------------------------------------
Spiralog 0 1
--------------------------------------------------------------------------------
Sysloa 4 (2 duplicates) 0
--------------------------------------------------------------------------------
Sys$vm 0 5 (3 duplicates)
--------------------------------------------------------------------------------
System_prim 1 0
--------------------------------------------------------------------------------
Utility
Analyze 0 0
DCL 0 2
Directory 0 0
Mail 1 0
Phone 0 2
Show 1 0
Sysman 0 1
--------------------------------------------------------------------------------
Verify 1 0
--------------------------------------------------------------------------------
Total 62 78
--------------------------------------------------------------------------------
Analysis:
SCSI drivers continue to plague our Alpha customers, especially customers
with TurboLASER systems (DEC 8400) configured with over 1.0GB of memory and
KZPSA SCSI adapters (SYS$PKSDRIVER). The Jul-Sep '96 Causal Analysis Report
also referenced SCSI drivers and Alpha systems configured with over 1GB of
memory. During GRYPHON Qual, QTV had 4 systems configured with 1GB or more
of memory (2 RAWHIDEs - 1GB and 1.384GB & 2 TurboLASERs - 3GB and 6GB).
RAVEN should also contain testing focus in this area with more ALPHAs
configured with >1GB of memory and tests designed to exercise these upper
memory boundaries.
On Vax systems, F11BXQP crashes (XQPERR & WCBFCBMNG) received the highest
number of IPMT Case reports during the Oct - Dec '96 timeframe. Customers
reported experiencing these crashes primarily on VAX 66xx & 76xx type
systems. As was reported in the Jul-Sep '96 Causal Analysis Report, EDO
does the majority of F11BXQP testing, but a testing void exists because
the site does not have access to larger/faster types of machines for testing
purposes. This same testing void is true for DECDTM, which is also tested at
EDO. Numerous DECDTM system crashes, primarily on 84xx systems, have also been
logged recently.
LAN (EWDRIVER & NET$FDDI) had multiple IPMT Cases logged due to system
crashes and errors (fatal error detected by datalink) reported after
configuring systems with multiple ethernet adapters.
Cases logged against DCE are also on the rise, although an examination of
these Cases indicate that DCE is the 'victim' not the cause of the problem
in many of these Cases. Code changes implemented in the DEC C runtime
library, FORTRAN runtime library, UCX, DECTHREADs, etc. have been found
to be the real cause of many of the DCE problems. Therefore, an increased
utilization of Distributed Computing Environments in testing areas could
potentially be a useful defect finding 'tool'.
|
|
.___.___.___.___.___.___.___.
! ! ! ! ! ! ! !
! d ! i ! g ! i ! t ! a ! l ! I N T E R O F F I C E M E M O
!___!___!___!___!___!___!___!
TO: OpenVMS Software Group
DATE: 11-Apr-1997
FROM: Tom Collins
DEPT: QTV Group
EXT: 381-1329
LOC: ZK03-4S02
ENET: VMSSPT::COLLINS
SUBJECT: OpenVMS CLD Causal Analysis Report
This report is an evaluation of the severity 1 and 2 IPMT Cases logged to
OpenVMS Sustaining Engineering during the 12 week period from Jan 1, 1997
to Mar 31, 1997. This report is made possible through the collaborative
efforts of the QTV Group and Sustaining Engineering Problem Management.
The purpose of this report is to identify the OpenVMS software component
areas where our installed base of customers are encountering the highest
amount of serious problems.
Note: A great deal of effort is made in the compilation of this analysis
to provide data that reflects the actual number of true OpenVMS component
problems reported by customers. Therefore the total numbers and component
areas shown in this report do not include severity 1 & 2 Cases logged
to Sustaining Engineering during this 12 week period that have been
closed with the following closure codes, indicating that the problems
are either non-OpenVMS component problems or there is insufficient
data to determine the root cause of the problem at this time.
Cases with the following closure codes were not included:
TR Transferred to another Engineering Group
TC Transferred to another CSSE group
UE User Error
US Unsupported in this version
HW Hardware Problem
II Insufficient Information
44 Not a valid problem
Overview: (Alpha)
During this 12 week period, 94 OpenVMS component problem reports were
logged against the Alpha Operating System.
2 were logged on Alpha V6.1, 43 on V6.2, 3 on V6.2-1H1, 8 on V6.2-1H2
23 on V6.2-1H3, 3 on V7.0, and 12 on V7.1.
Overview: (VAX)
On VAX, 53 OpenVMS component problem reports were logged during this period.
3 Cases were logged on V5.5-2, 7 on V5.5-2H4, 13 on V6.1, 21 on V6.2,
1 on V7.0, and 8 on V7.1.
The Case breakdown per component area for Alpha was the following;
==========================================================================
Customer Hardware_type OS_version Product Component
DMI INC 7.1 ARGUS
Pacific Bell Dir 6.2 BACKUP
Catholic Health 2100 4/275/1.5GB 6.2 CLUSTER CNX
UNIVERSITY OF WAIKAT 1000A 4/300/256MB 6.2-1H3 CLUSTER LCK
TELKOM 2100 5/250 6.2 CLUSTER LCK
Digital 3000/600/128MB 7.1 CLUSTER MOUNT
UNIBANK 8400 EV56/2GB 6.2-1H3 CLUSTER MSCP
Minstry of Natl Res 8400 6.2 CLUSTER SCS$
Information America 3000 700/320MB 6.2 CLUSTER SCS$
Japan Telecom 8400 5/300 6.2-1H3 CLUSTER SHADOWING
Tokyo Gas 8400 5/350/2GB 6.2 CLUSTER SHADOWING
Bankers Trust 2100/640MB 6.2 CLUSTER SHADOWING
Royal Bank of Scotland 8400 5/300/2GB 6.2 CLUSTER SHADOWING
AIG Financial products 8400 5/300 6.2 CLUSTER SHADOWING
RIEM 7640/2.5GB 7.1 CLUSTER TMSCP
Factset Data Systems 8400 EV56/440 6.2-1H3 COMM FTDRIVER
Lockheed Martin 8400 6.2-1H3 COMM OPDRIVER
Evans Griffiths and Hart 2000 7.1 COMM RTDRIVER
PARANOR AG 2100 5/300 6.2-1H2 DCE
MCI MASS MARKETS NEWPORT 2100/1.5GB 6.2 DCE
DIGITAL EQUIPMENT CORP 2100 4/200 6.2 DECDFS
Nihon Telecom (NTT) 8400/4GB 6.2 DECDTM
QUINTILES INC 8400 5/300 6.2 DECDTM
Mitel Corp. 2100 5/250/256MB 6.2 DRIVER FYDRIVER
HOFFMANN-LA ROCHE AG 8400 5/300/2GB 7.1 DRIVER DUDRIVER
Pacific Bell 8400/4GB 6.2 DRIVER DUDRIVER
Blockbuster Information AS255 6.2-1H2 DRIVER OPDRIVER
MCI MASS MARKETS MEMPHIS 2100 5/250/1.5GB 6.2 EXEC SETPFM
MCI MASS MARKETS SPRINGFLD 2100 5/250/1.5GB 6.2 EXEC GET_SECURITY
Sonda Computacion 6.2 EXEC IMAGE_MAN
Pioneer Concrete 6.2 EXEC SETP0
Alcatel SEL AG AS400/64MB 7.1 EXEC IOROUTINES
Koninklijk Nederlands Metr 1000 4/266/128MB 6.2 EXEC SYS$VM
VCS NACHRICHTENTECHNIK 2000 4/275/512MB 6.2-1H3 EXEC SYS$VM
CREDIT UNION CENTRAL 7740/3GB 6.1 EXEC SYS$VM
MCI MASS MARKETS MEPHIS S 2100 5/250/1.5GB 6.2 EXEC SYS_PRIM
Denison Univ 250 4/266/192MB 6.2-1H1 EXEC SYSINIT
JAPAN TELECOM 8400/4GB 6.2-1H3 F11 XQP
RIEM 4X00 5/400/1GB 7.1 F11 XQP
DOC/NOAA/NOS/ACD/ACAB 2100 6.2 F11 XQP
Bank Austria 8400 5/300/2GB 6.2 INFOSRVR LASTDRIVER
BAPTIST MEMORIAL HOSP 2100A 4/275/512MB 6.2-1H2 INFOSRVR MADDRIVER
MEIDENSYA 8200 5/300/640Mb 6.2 JVMS
AGIP SPA 1000 6.2 LAN ERDRIVER
Norwich Union Life 2000 4/200 6.2-1H2 LAN IRDRIVER
Lockheed Martin 8400 6.2 LAN EWDRIVER
Modern Terminals 8200 6.2 LAN FXDRIVER
Bank Austria 8400 6.2 LAN FXDRIVER
Japan Telecom 2100 6.2 LAT
SERVICIOS ADMINISTRA 2000 6.2-1H1 LATSYM
Supra-Fama 8400 5/350/6GB 6.2-1H3 QMAN
USPS/00-05-68910 8400 EV56/440 6.2-1H3 QMAN
C I S TECHNOLOGIES INC 2100 4/275 7.0 RMS
DAGAB AB 4100/3GB 6.2-1H3 SCSI DKDRIVER
Bell Helicopter 2100 5/250/512MB 6.2-1H3 SCSI DKDRIVER
Palmer College 3000 300/160MB 6.2 SCSI DKDRIVER
Reuben H. Donnelley 2100 5/250/512MB 6.2-1H3 SCSI DKDRIVER
Affiliated University 6.2 SCSI DKDRIVER
Barco Graphics 3000 500 6.2-1H3 SCSI DKDRIVER
Generaldirektion PTT 2100A 5/300/512MB 6.2-1H2 SCSI DKDRIVER
Cell One 4100 5/300/2MB 6.2-1H3 SCSI DKDRIVER
Puget Sound Power and Lgt 2100 5/250 6.2 SCSI DKDRIVER
Uni Of Hartford 1000 4/200/128MB 7.1 SCSI DKDRIVER
Kinetic Systems 3000 400 6.2 SCSI GKDRIVER
SD Labs 4100 6.2 SCSI MKDRIVER
KWIK FIT 2100/512mb 6.2-1H2 SCSI MKDRIVER
Dow Chemical 3000 500 6.1 SCSI PKCDRIVER
Genzyme AS1000 6.2-1H1 SCSI PKEDRIVER
Protec AS400 233/96MB 7.1 SCSI PKEDRIVER
CAPRAL ALUMINIUM LIM 1000A 4/266/64MB 6.2 SCSI PKQDRIVER
EMPRESA NACIONAL DE ELEC 4100/512MB 6.2 SCSI PKQDRIVER
NOTTINGHAM UNIVERSITY 6.2-1H3 SCSI PKQDRIVER
Total Access Community 8400 5/300 6.2-1H3 SCSI PKQDRIVER
CITY OF RALEIGH 8400 6.2 SCSI PKQDRIVER
TCG 2150/256MB 6.2-1H3 SCSI PKSDRIVER
Florida State University 3000 400 6.2-1H2 SCSI PKSDRIVER
OM SYSTEMS INTERNATIONAL 1000A 5/300/832MB 6.2-1H3 SCSI PKSDRIVER
CLS-SERVICE ARGOS 1000A 5/400/512MB 7.1 SCSI PKSDRIVER
NTTDATA Telecommunication 1000 4/266/256MB 6.2 SECURITY AUDITSRVR
Healthcare Compare 6.2 SECURITY AUDITSRVR
Genex LTD 2100 5/300 6.2 SECURITY AUDITSRVR
Cedars-Sanai Medical Ctr 2100 4/275/640MB 6.2-1H3 SECURITY OPCOM
Banco Internacional 10000/1.5GB 6.2 SECURITY SECURITY_S
McDonnel Douglas/FLTSIM 2100 4/233/128MB 7.1 SYS EXEC_INIT
Boston Warer & Sewer Com 1000A 5/333 6.2-1H3 SYS SYSBOOT
The Budd Company 6.2 UTILITY AUTOGEN
GSI MBH AS400 4/233 6.2-1H3 UTILITY COPY
HSQ Technology Inc 3000 700/64MB 7.0 UTILITY DCL
Stanford University 3000 600/96MB 7.0 UTILITY DCL
Cellular One 2100 6.2 UTILITY DIRECTORY
Optical Waveguides 7.1 UTILITY EDIT
Japan Telecom 8400/4GB 6.2-1H3 UTILITY SHOW
TELEFONICA SERVICIOS 8400 EV56/440/2GB 6.2-1H3 VERIFY
Bankers Trust Australia 2100 4/275/512MB 6.2-1H2 VMS
The Case breakdown per component area for VAX was the following;
==========================================================================
Customer Hardware_type OS_Version Product Component
Bell Comm 6510/512MB 7.1 AUDIT_SRVR
Banco Pastor 6610/128MB 6.2 BACKUP
Pacific Bell Directory 43JS1 6.2 BACKUP
Pacific Bell Directory 43JS1 6.2 BACKUP
Combitech Network AB 4000/90 6.2 BACKUP
TSMC-OSMA 7000 5.5-2 BRS
ENGEL MAS. 4100/128MB 6.1 CLUSTER CNX
Micron 7730 6.1 CLUSTER CNX
Bell Comms 6610/512MB 7.1 CLUSTER MOUNT
Bell Comm 6510/512MB 7.1 CLUSTER SHADOWING
DIGITAL - SD LABS 4300 7.1 CLUSTER SHADOWING
Bell Core 6510/512MB 7.1 CLUSTER SHADOWING
British Telecom - Cellnet 7730 6.1 CLUSTER SHADOWING
CORNELL UNIVERSITY - 901 7.1 DECDFS
US Air Force 6400 6.2 DRIVER DUDRIVER
Bank of America 6620/512MB 6.2 DRIVER FYDRIVER
UNIV OF ARIZONA CCIT 7.1 DRIVER NODRIVER
Intel Ireland FAB10 7660/512MB 6.1 EXEC QUEUEMPTY
ELi Lilly & Co 7660/512MB 6.2 EXEC QUEUEMPTY
Copley Computer Services 7620/512MB 6.2 EXEC IOROUTINES
Pioneer Concrete 6.2 EXEC SETP0
ST CLOUD STATE UNIV 4700A/512MB 6.2 F11 XQP
DTB 10830/256MB 6.2 F11 XQP
YAMAHA TOYOOKA 4500A 5.5-2H4 F11 XQP
INTEL CORP/A4/FAB6 6620 5.5-2 F11 XQP
BOWNE Information Systems 6420 6.2 F11 XQP
Capital City Press 6.1 F11 VERIFY
HEALTH NET INC 7740 6.1 INFOSRVR LASTDRIVER
Joint Defence Facili 6610 6.2 INFOSRVR LASTDRIVER
EDS Canada 4700 6.2 INTERNAL $ SDA
TOKYO GAS 6.1 JVMS
DOW CHECMICAL Co 5.5-2 KITS
Ced Borsa 7640/512MB 6.2 LAN NET$CSMACD
Integrated System Solutns 3195 6.2 LAN EZDRIVER
Vodacom 7720 6.1 LAN FXDRIVER
Actew Corporation 7000 5.5-2H4 LAN FXDRIVER
ABC 6.2 LAN FXDRIVER
PACIFIC POWER 7720 6.1 LAT LTDRIVER
MINNESOTA HOUSING FINANCE 4600 7.0 LAT LTDRIVER
EU-LOG-SYSTEM MGMT 4300 6.2 LAT LTDRIVER
Siemens AG 7620 5.5-2H4 POSIX
Bosch Telecom GMBH 4100 5.5-2H4 POSIX
Siemens AG 7000 6.1 POSIX
Siemens AG 7000 6.1 POSIX
MCI - NCS 6620 6.2 RMS JNL
Federal HOME loan Bank Brd 3100/32MB 6.1 SCSI DKDRIVER
CHAMBOURCY 4000/60 5.5-2H4 SCSI DKDRIVER
R R Donnelley 4100A/64MB 5.5-2H4 SCSI PKBDRIVER
Landis & Gyr 4090/64MB 5.5-2H4 SCSI PKBDRIVER
TOWN OF HUDSON 4000/50 6.2 SCSI PKCDRIVER
Michelin 6610 6.2 SECURITY SECURITY_S
VOLVO CARS EUROPE INDUSTRY 6.1 TSM
Bell Communications Rescrh 6510/128MB 7.1 UTILITY SET
Analysis (Alpha):
SCSI port and class drivers continue to plague our Alpha customers.
4 of the 10 DKDRIVER Cases reported a system crash that occurred
while running HSZTERM during heavy I/O, resulting in an INVEXCEPTN
in SYS$PKSDRIVER attempting to access a Queue Buffer. 1 case reported
an INCONSTATE crash in SYS$DKDRIVER if mount verification occurs
while a DK device is reporting a write-locked condition. Another
customer reported a problem mounting RZ73/RZ74 disks on system
reboot, after a powerfail, because DKDRIVER's disconnect timeout was
too short to allow the RZ73/RZ74 to finish spinning up. 4 of the 5
Cases reported on PKQDRIVER dealt with corruption of the ERASE PATTERN
BUFFER if an unaligned read (partial block) was requested to a disk
connected to a PKQDRIVER port. Another customer reported being plagued
with multiple mount verifications on SCSI disks during BACKUP, which
was due to the drive sending a Queue Full status and DKDRIVER returning
MEDOFL, which resulted in the mount verification and a SYSTEM-W-NOTQUEUED
errorlog entry. SYS$PKEDRIVER on V7.1 caused mount verifications and hangs
when an async device was used after a sync device had been accessed.
5 Cases were reported on the SHADOWING component by customers running
the SHADOW code images (not SHADOW96). 4 of the 5 Cases were attributed
to known SHADOW driver problems and these customers were requested to
upgrade to the ALPCLUSIO kit (SHADOW96). 1 Case involved shadowsets
connected to dual-redundant HSJ40s, when 1 HSJ40 failed (ECC error),
the shadowsets connected thru the failing HSJ40 went into mount
verification, then to 'ZERO WORKING MEMBERS', after MVTIMEOUT expired
(shadow members never failed over to the other HSJ40). This was a 1 time
occurrence at the customer site and attempts to reproduce this scenario
in Engineering have been unsuccessful.
XQP received reports of XQPERR crashes that occurred during the processing
of a directory file due to not finding any free directory index buffer
descriptors (BFRDs) on a first pass through MAKE_DIRINDX (i.e. low
ACP_DINDXCACHE value could cause this to occur). Japan Telecom reported
multiple allocated block problems on a 2 member shadow set, each member
being a 6 disk RZ29 stripeset. The corruption was due to an XQP
syncronization problem causing a node to think its cached data was valid
when in-fact it wasn't. Japan Telecom's cluster consists of 5-8400
(10 CPUs each).
note: The XQP test group does not have 8400 systems available in its cluster
to utilize for testing purposes.
Customers reported 2 Cases against the LAN facility due to problems
between the LAN drivers and CISCO routers. One Case involved Alphaserver
1000s, running PATHWORKS and UCX, crashed (INVEXCEPTNs) after upgrading
the firmware on their CISCO routers. Another customer with a dual FDDI,
dual ring configuration tied by CISCO routers, running DECNET/OSI and UCX,
encounterd dynamic routing problems when the FDDI cable was removed from
one of the rings.
Analysis (VAX):
The 5 XQP cases logged on VAX are still under investigation at this
time. The problems involve XQPERR crashes that have occurred when
using a disk defragger or dismounting a jukebox drive and encountering an
invaild lock ID. Another report of a NOTFCBFCB crash (FCB linkage broken)
was also logged. All reports of this problem seem to involve the
PSDC$DC_SERVER, but the root cause has not been determined.
SD Labs has reported a problem using V7.1 with the SHADOW96 code. Attempting
to boot a 2nd node off of a 2 member system disk shadowset results in the
2nd node crashing with a SHADDETINCON. Another customer reported MERGE
operations being initiated on shadowsets after a node, with a CSB$W_CNID=0,
exited the cluster, eventhough the node exiting did not have the shadowsets
mounted.
Bell Core has been experiencing problems in testing on their development
cluster with the new (V7.1) MOUNT96 code due to a behavior change in the
volume label check for shadowsets between the old MOUNT and MOUNT96.
3 of the 4 POSIX Cases logged, involved a POSIXBUG crash which was attributed
to a race condition in the kernel code associated with signaling and
message passing.
SCSI crashes were reported in DKDRIVER if a customer issued an IO$_AUDIO
command to a DK device if an invalid AUCB was specified. It resulted in
either an INVEXCEPTN or DOUBLDEALO bugcheck.
Issues related to BACKUP included; slow backup on a 2nd tape volume (SA100)
due to a write-back cache problem, problems restoring selective files in
directories deeper than 8 directories, and updating a directory (i.e. security
attributes) results in the entire directory contents and subdirectory
contents to be backed up.
Future Considerations:
Sustaining Engineering currently is working on an ALPSCSI01 remedial kit.
The kit is planned to contain 13 SCSI drivers with 40+ bugfixes for these
drivers. Although Sustaining has target tested the individual fixes
contained in this kit, a system level testing focus of the complete
kit needs to be accomplished as soon as possible, so that customers
can acquire the benefits of these SCSI fixes in the near future.
Past issues / Current progress:
Increased SCSI driver testing focus is needed, utilizing an assortment of
3rd party SCSI devices in the test environment (Apr-Jun '96 report).
QTV evaluated using a SCSI emulator to accomplish this, but
it was decided that the emulator would not suffice for QTV's
testing requirements. Currently, QTV is compiling a list of
3rd party SCSI devices needed for testing.
More testing focus needed on systems configured with greater than
2.0GB of memory (Jul-Sep '96 report).
QTV has purchased another Tlaser, so QTV now has 1 Tlaser with
5GB of memory and another Tlaser with 4GB of memory for testing
purposes.
CIPCA/KFMSB/CIXCD testing has been done on systems with GT 8GB
MEMORY CHANNEL testing was done on systems with GT 8GB
Memory hole testing was done on 2 Rawhides with GT 4GB
QTV took advantage of the 28GB Tlaser array for additional testing
An investigation is currently in progress with participants from
QTV, Sustaining, and the Cluster I/O group to determine what
tools should be utilized to optimize testing in large memory
configurations.
F11BXQP (EDO) test cluster doesn't have access to more powerful systems
such as LASER/TurboLASER platforms (Oct-Dec '96 report).
Ian Compton from the EDO testing group spent a week in ZKO during
March 1997. During that week he spent some time with the QTV
Group discussing whether the EDO test group should become part
of QTV. The results of that discussion are the following;
- The EDO testing group will only be AFFILIATED with QTV
- They will have no reporting structure into QTV
- The EDO testing group may change its name to QTV-Scotland
- EDO will participate in QTV's monthly communications meetings
so they will have a better idea of what's going on in the
States
- They will report their monthly status through Chris Shaver's
monthly report as well as through Mark Howell's report
- Ian and Chris Shaver will meet via phone on a monthly basis
|