Hello Managers -
Our Digital Unix machine is an AlphaServer 800 5/500 running 4.0E.
We're getting several of these messages everyday in the
/usr/var/adm/messages file:
Jan 26 02:39:37 sif vmunix: AdvFS I/O error:
Jan 26 02:39:37 sif vmunix: Domain#Fileset: disk07#u07
Jan 26 02:39:37 sif vmunix: Mounted on: /disk07
Jan 26 02:39:37 sif vmunix: Volume: /dev/rz10c
Jan 26 02:39:37 sif vmunix: Tag: 0x0000015b.8014
Jan 26 02:39:37 sif vmunix: Page: 82
Jan 26 02:39:37 sif vmunix: Block: 7381888
Jan 26 02:39:37 sif vmunix: Block count: 256
Jan 26 02:39:37 sif vmunix: Type of operation: Read
Jan 26 02:39:37 sif vmunix: Error: 5
Jan 26 02:39:37 sif vmunix: To obtain the name of the file on which
Jan 26 02:39:37 sif vmunix: the error occurred, type the command:
Jan 26 02:39:37 sif vmunix: /sbin/advfs/tag2name /disk07/.tags/347
When I type in the command:
/sbin/advfs/tag2name /disk07/.tags/347
I get:
/disk07/oradata/upgrade/back_d4/log01a.dbf.Z
My (rather uneducated) suspicion is that it's a bad disk drive (I could
certainly be wrong, though) so I went to the:
/etc/fdmns/disk07
directory and issued:
sif_root> ls -alF
which displayed:
total 16
drwxr-xr-x 2 root system 8192 Oct 27 10:56 ./
drwxr-xr-x 12 root system 8192 May 24 1999 ../
lrwxrwxrwx 1 root system 10 Jul 1 1998 rz10c_at_ -> /dev/rz10c
lrwxrwxrwx 1 root system 10 Jun 28 1999 rz17g_at_ -> /dev/rz17g
lrwxrwxrwx 1 root system 10 Oct 27 10:56 rz18d_at_ -> /dev/rz18d
I take it then that our logical /disk07 is made up of three physical
devices, rz10c, rz17g, and rz18d.
But now I'm at a dead-end of my knowledge. Is there a way I can determine
which of these devices could be the culprit?
What is the significance, if any, of:
Volume: : /dev/rz10c
in the message? Is that just the first volume in the fdmns file or is that
the device with the bad Read ?
Many thanks!
Andy Cohen
Oracle Database Administrator
Cognex Corporation
1 Vision Drive
Natick, MA 01760-2059
v: 508/650-3079
f: 508/650-3337
e: acohen_at_cognex.com
Received on Wed Jan 26 2000 - 21:08:00 NZDT