SUMMARY: Error with 4.0D, advfsd and HSZ50

From: Malczewski, Damien <DMalczewski_at_ricegrowers.com.au>
Date: Tue, 17 Nov 1998 09:52:33 +1100

Thanks goes to :

Kym Schwarz [schwarz_at_stl.dec.com]
alan_at_nabeth.cxo.dec.com
C.Ruhnke [i769646_at_smrs013a.mdc.com]
georg.tasman_at_db.com
Bryan Lavelle [Bryan.Lavelle_at_digital.com]

Answer :

Of course since the other servers in the cluster can see the disks but
cannot access them, advfsd likes to complain about it. The trick is to
either stop the advfsd from starting, but I use Performance Manager so this
wasn't a good solution OR add a file called /var/opt/advfsd/disks.ignore and
add to it the list of disks advfsd shouldn't scan. E.G.

/var/opt/advfsd/disks.ignore

rz24
rzb24
rz25
rz26
rzb26
rzc26
rzd26
rze26

Thanks,
Damien.


> -----Original Message-----
> From: Malczewski, Damien
> Sent: Monday, November 16, 1998 3:07 PM
> To: alpha-osf-managers_at_ornl.gov
> Subject: Error with 4.0D, advfsd and HSZ50
>
>
> Managers,
>
> I am having a strange problem with my recently upgraded (to DU 4.0D)
> alpha servers. The advfsd daemon, when it wakes up on it's 5 minute
> interval, drops a lot of errors in the binary.errlog. It only errors on
> the servers that do not have access to a groups of disks on a HSZ
> controller.
>
> Is it a HSZ firmware issue? Advfs error?
>
> Advfs is version 425
> System is on Firmware 5.0 (A11 version of SCSI firmware)
>
>
> A typical uerf entry viewed through dia would look look :
>
> ******************************** ENTRY 1
> ********************************
>
>
> Logging OS 2. Digital UNIX
> System Architecture 2. Alpha
> Event sequence number 161.
> Timestamp of occurrence 16-NOV-1998 14:48:20
> Host name green
>
> System type register x00000016 Alpha 4000/1200 Series
> Number of CPUs (mpnum) x00000002
> CPU logging event (mperr) x00000001
>
> Event validity 1. O/S claims event is valid
> Event severity 5. Low Priority
> Entry type 199. CAM SCSI Event Type
>
>
> ------- Unit Info -------
> Bus Number 4.
> Unit Number x0114 Target = 2.
> LUN = 4.
> ------- CAM Data -------
> Class x00 Disk
> Subsystem x00 Disk
> Number of Packets 4.
>
> ------ Packet Type ------ 258. Module Name String
>
> Routine Name cdisk_op_spin
>
> ------ Packet Type ------ 256. Generic String
>
> Unit Reserved
>
> ------ Packet Type ------ 262. Info Error String
>
> Error Type Information Message Detected
> (recovered)
>
> ------ Packet Type ------ 257. Device Name String
>
> Device Name DEC HSZ50-AX V50Z
>
> ********************************
>
> Thanks,
> Damien.
>
>
Received on Mon Nov 16 1998 - 22:54:01 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:38 NZDT