Summary: ADVFS error

From: Rolf-Peter Kienzle <kienzlep_at_uni-freiburg.de>
Date: Mon, 17 Jan 2000 00:58:43 +0100

Dear managers!

I've had some weird AdvFS errors concerning Quantum SCSI disks after
upgrading from V4.0B PK10 to V4.0F PK2. But now, after re-installing the
original OS version everything is fine again. So the problem isn't
really solved but my servers keep on running!

Regards

Peter

Original message follows:

I encountered the following AdvFS error on two disks on one of my
servers (AS 200 4/166, DU 4.0F, PK2):

Jan 2 22:03:39 server vmunix: AdvFS I/O error:
Jan 2 22:03:39 server vmunix: Volume: /dev/rz9g
Jan 2 22:03:39 server vmunix: Tag: 0xfffffffa.0000
Jan 2 22:03:39 server vmunix: Page: 67
Jan 2 22:03:39 server vmunix: Block: 12352
Jan 2 22:03:39 server vmunix: Block count: 16
Jan 2 22:03:40 server vmunix: Type of operation: Write
Jan 2 22:03:40 server vmunix: Error: 5
Jan 2 22:03:40 server vmunix:
Jan 2 22:03:40 server vmunix: bs_osf_complete: metadata write failed
Jan 2 22:03:40 server vmunix: AdvFS Domain Panic; Domain user17_dmn Id
0x35028ebe.0004b672
Jan 2 22:03:40 server vmunix: An AdvFS domain panic has occurred due to
either a metadata write error or an internal inconsistency. This domain
is being rendered inaccessible.
Jan 2 22:03:40 server vmunix: Please refer to guidelines in AdvFS Guide
to File System Administration regarding what steps to take to recover
this domain.
Jan 2 22:03:40 server vmunix: AdvFS I/O error:
Jan 2 22:03:40 server vmunix: Volume: /dev/rz9g
Jan 2 22:03:40 server vmunix: Tag: 0xfffffffa.0000
Jan 2 22:03:40 server vmunix: Page: 77
Jan 2 22:03:40 server vmunix: Block: 12512
Jan 2 22:03:40 server vmunix: Block count: 16
Jan 2 22:03:40 server vmunix: Type of operation: Write
Jan 2 22:03:40 server vmunix: Error: 5
 ... more

The only way to recover from this error is to reboot the machine because
the disks are no longer accessible (annoying ...). Verifying the disks
after the reboot reveals nothing unusual. Subsequently, the disks appear
to function normally.

I defragment my disks regularly at 10pm. I upgraded the OS to version
4.0F recently (Y2K, you know). I have never come across this kind of
error when I was running V4.0B. Any clues what could go wrong?

-- 
Dipl.-Phys. Rolf-Peter Kienzle
Dept. of Remote Sensing and Land Information Systems
University of Freiburg, D-79085 Freiburg, Germany
Tel/Fax +49 761 203 8643/8640 e-mail: kienzlep_at_uni-freiburg.de
Received on Sun Jan 16 2000 - 23:59:53 NZDT

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