From: bryan.mills@lynx.co.uk
Date: Tue May 28 2002 - 10:19:11 EDT
I have a HSG80 with a 3 way mirror which has just been installed. This
morning the system hung, the application reported write failures and upon
rebooting the file sets on this file domain won't mount. One of the
write lights on a physical disk has stayed on, so I'm guessing that the
fault lies there. 2 questions if anyone can assist. Firstly, how / why
did this happen, secondly, why hasn't the system carried on and dropped
one of the mirrors out ? Error messages below from /var/adm/messages.
TRU64 5.1A, no patchkits yet
May 28 12:13:23 gs60TEST vmunix: AdvFS I/O error:
May 28 12:13:23 gs60TEST vmunix: Volume: /dev/disk/dsk12c
May 28 12:13:23 gs60TEST vmunix: Tag: 0xfffffff6.0000
May 28 12:13:23 gs60TEST vmunix: Page: 2176
May 28 12:13:23 gs60TEST vmunix: Block: 113830704
May 28 12:13:23 gs60TEST vmunix: Block count: 16
May 28 12:13:23 gs60TEST vmunix: Type of operation: Write
May 28 12:13:23 gs60TEST vmunix: Error: 5
May 28 12:13:23 gs60TEST vmunix: EEI: 0x6400
May 28 12:13:23 gs60TEST vmunix: I/O error appears to be due to a
hardware problem.
May 28 12:13:23 gs60TEST vmunix: Check the binary error log for
details.
May 28 12:13:23 gs60TEST vmunix:
May 28 12:13:23 gs60TEST vmunix: bs_osf_complete: metadata write failed
May 28 12:13:23 gs60TEST vmunix: AdvFS Domain Panic; Domain lynx Id
0x3cb2bcf8.0008db7e
May 28 12:13:23 gs60TEST vmunix: An AdvFS domain panic has occurred due
to either a metadata write error or an internal inconsistency. This
domain is being rendered inaccessible.
May 28 12:13:23 gs60TEST vmunix: Please refer to guidelines in AdvFS
Guide to File System Administration regarding what steps to take to
recover this domain.
May 28 12:13:23 gs60TEST vmunix: Domain panic appears to be due to a
hardware problem
May 28 12:13:23 gs60TEST vmunix: Check the binary error log for more
information
.
May 28 12:13:23 gs60TEST vmunix: AdvFS I/O error:
May 28 12:13:23 gs60TEST vmunix: A read failure occurred - the AdvFS
domain is inaccessible (paniced)
May 28 12:13:23 gs60TEST vmunix: Domain#Fileset: lynx#lynx_data
May 28 12:13:23 gs60TEST vmunix: Mounted on: /lynx_data
May 28 12:13:23 gs60TEST vmunix: Volume: /dev/disk/dsk12c
May 28 12:13:23 gs60TEST vmunix: Tag: 0x00000004.8001
May 28 12:13:23 gs60TEST vmunix: Page: 0
May 28 12:13:23 gs60TEST vmunix: Block: 464
May 28 12:13:23 gs60TEST vmunix: Block count: 16
May 28 12:13:23 gs60TEST vmunix: Type of operation: Read
May 28 12:13:23 gs60TEST vmunix: Error: 5
May 28 12:13:23 gs60TEST vmunix: EEI: 0x300
May 28 12:13:24 gs60TEST vmunix: To obtain the name of the file on
which
May 28 12:13:24 gs60TEST vmunix: the error occurred, type the
command:
May 28 12:13:24 gs60TEST vmunix: /sbin/advfs/tag2name
/lynx_data/.tags/4
May 28 14:42:11 gs60TEST vmunix: Alpha boot: available memory from
0x17da000 to 0x1ff5a000
This message is intended only for the use of the person(s) ("The intended
Recipient(s)") to whom it is addressed. It may contain information which
is privileged and confidential within the meaning of applicable law. If
you are not the intended recipient, please contact the sender as soon as
possible. The views expressed in this communication are not necessarily
those held by LYNX Express Limited.
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:42 EDT