Folks,
Ignorance question here, if you don't mind.
We're seeing this timeout error -- "relog syslog SCSI drive 6.0 max timeout count exceeded" followed by "Resetting SCSI bus 6 (ha #3)".
However, sysconfig -r doesn't show drive 6.0 on ha id 3 anywhere.
Could someone please explain what's going on here?
Thanks much.
Dave
Stephen Lasseter wrote:
Fri Nov 19 00:00:01 GMT [smith: statd]: 12:00am up 25 days, 2:48 169239880 NFS ops, 0 CIFS ops, 63 HTTP ops Fri Nov 19 01:00:01 GMT [smith: statd]: 1:00am up 25 days, 3:48 169345577 NFS ops, 0 CIFS ops, 63 HTTP ops Fri Nov 19 02:00:01 GMT [smith: statd]: 2:00am up 25 days, 4:48 169451567 NFS ops, 0 CIFS ops, 63 HTTP ops Fri Nov 19 02:20:08 GMT [smith: isp_timeout]: 6.0(0xfffffc0000e84180): command timeout, retrying request Fri Nov 19 02:20:08 GMT [smith: isp_timeout]: Resetting SCSI bus 6 (ha #3) Fri Nov 19 02:25:34 GMT [smith: isp_timeout]: 6.0(0xfffffc0000e84660): command timeout, retrying request Fri Nov 19 02:25:34 GMT [smith: isp_timeout]: Resetting SCSI bus 6 (ha #3) Fri Nov 19 02:32:05 GMT [smith: rc]: de_main: e0 : Link up. Fri Nov 19 02:32:05 GMT [smith: rc]: relog syslog Fri Nov 19 02:30:53 GMT [smith: isp_timeout]: 6.0(0xfffffc0000e84b40): command timeout, retrying request
Fri Nov 19 02:32:05 GMT [smith: rc]: relog syslog SCSI drive 6.0 max timeout count exceeded - system resetting to recover!
Fri Nov 19 02:32:05 GMT [smith: rc]: NetApp Release 5.2.1P2 boot complete. Last disk update written at Fri Nov 19 02:30:22 GMT 1999
smith> sysconfig -r Volume brs1
RAID group 0
RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks)
parity 0a.8 0a 1 0 FC:A 17000/34816000 17366/35566480 data 0a.1 0a 0 1 FC:A 17000/34816000 17366/35566480 data 0a.4 0a 0 4 FC:A 17000/34816000 17366/35566480 data 0a.0 0a 0 0 FC:A 17000/34816000 17366/35566480 data 0a.5 0a 0 5 FC:A 17000/34816000 17366/35566480 data 0a.13 0a 1 5 FC:A 17000/34816000 17366/35566480 data 0a.10 0a 1 2 FC:A 17000/34816000 17366/35566480 data 0a.3 0a 0 3 FC:A 17000/34816000 17366/35566480 data 0a.11 0a 1 3 FC:A 17000/34816000 17366/35566480 data 0a.9 0a 1 1 FC:A 17000/34816000 17366/35566480 data 0a.2 0a 0 2 FC:A 17000/34816000 17366/35566480 data 0a.28 0a 3 4 FC:A 17000/34816000 17366/35566480 data 0a.29 0a 3 5 FC:A 17000/34816000 17366/35566480 data 0a.30 0a 3 6 FC:A 17000/34816000 17366/35566480
Volume spool (root)
RAID group 0
RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks)
parity 0a.12 0a 1 4 FC:A 17000/34816000 17366/35566480 data 0a.14 0a 1 6 FC:A 17000/34816000 17366/35566480 data 0a.6 0a 0 6 FC:A 17000/34816000 17366/35566480
Volume inbox
RAID group 0
RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks)
parity 0a.17 0a 2 1 FC:A 17000/34816000 17366/35566480 data 0a.16 0a 2 0 FC:A 17000/34816000 17366/35566480 data 0a.18 0a 2 2 FC:A 17000/34816000 17366/35566480 data 0a.21 0a 2 5 FC:A 17000/34816000 17366/35566480 data 0a.22 0a 2 6 FC:A 17000/34816000 17366/35566480 data 0a.24 0a 3 0 FC:A 17000/34816000 17366/35566480 data 0a.25 0a 3 1 FC:A 17000/34816000 17366/35566480
Volume hostapp
0a 1 4 FC:A 17000/34816000 17366/35566480 data 0a.14 0a 1 6 FC:A 17000/34816000 17366/35566480 data 0a.6 0a 0 6 FC:A 17000/34816000 17366/35566480
Volume inbox
RAID group 0
RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks)
parity 0a.17 0a 2 1 FC:A 17000/34816000 17366/35566480 data 0a.16 0a 2 0 FC:A 17000/34816000 17366/35566480 data 0a.18 0a 2 2 FC:A 17000/34816000 17366/35566480 data 0a.21 0a 2 5 FC:A 17000/34816000 17366/35566480 data 0a.22 0a 2 6 FC:A 17000/34816000 17366/35566480 data 0a.24 0a 3 0 FC:A 17000/34816000 17366/35566480 data 0a.25 0a 3 1 FC:A 17000/34816000 17366/35566480
Volume hostapp
RAID group 0
RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks)
parity 0a.20 0a 2 4 FC:A 17000/34816000 17366/35566480 data 0a.19 0a 2 3 FC:A 17000/34816000 17366/35566480
Spare disks
RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks)
spare 0a.27 0a 3 3 FC:A 0 17366/35566480 spare 0a.26 0a 3 2 FC:A 0 17366/35566480
Partner disks
RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks)
partner 1.0 1 0 0 FC:B 0 17366/35566480 partner 1.1 1 0 1 FC:B 0 17366/35566480 partner 1.2 1 0 2 FC:B 0 17366/35566480 partner 1.3 1 0 3 FC:B 0 17366/35566480 partner 1.4 1 0 4 FC:B 0 17366/35566480 partner 1.5 1 0 5 FC:B 0 17366/35566480 partner 1.6 1 0 6 FC:B 0 17366/35566480 partner 1.8 1 1 0 FC:B 0 17366/35566480 partner 1.9 1 1 1 FC:B 0 17366/35566480 partner 1.10 1 1 2 FC:B 0 17366/35566480 partner 1.11 1 1 3 FC:B 0 17366/35566480 partner 1.12 1 1 4 FC:B 0 17366/35566480 partner 1.13 1 1 5 FC:B 0 17366/35566480 partner 1.18 1 2 2 FC:B 0 17366/35566480 partner 1.19 1 2 3 FC:B 0 17366/35566480 partner 1.20 1 2 4 FC:B 0 17366/35566480 partner 1.14 1 1 6 FC:B 0 17366/35566480 partner 1.16 1 2 0 FC:B 0 17366/35566480 partner 1.17 1 2 1 FC:B 0 17366/35566480 partner 1.22 1 2 6 FC:B 0 17366/35566480 partner 1.21 1 2 5 FC:B 0 17366/35566480 partner 1.32 1 4 0 FC:B 0 17366/35566480 partner 1.33 1 4 1 FC:B 0 17366/35566480 partner 1.34 1 4 2 FC:B 0 17366/35566480 partner 1.35 1 4 3 FC:B 0 17366/35566480 partner 1.36 1 4 4 FC:B 0 17366/35566480 partner 1.37 1 4 5 FC:B 0 17366/35566480 partner 1.38 1 4 6 FC:B 0 17366/35566480 smith> -Steve
Any chance there is a tape drive attached there. We've seen this in the past and I've been caught twice with it reporting a relog on a SCSI drive, when what it really means is SCSI device.
Dave
Dave Toal wrote:
Folks,
Ignorance question here, if you don't mind. We're seeing this timeout error -- "relog syslog SCSI drive 6.0 max timeout count exceeded" followed by "Resetting SCSI bus 6 (ha #3)". However, sysconfig -r doesn't show drive 6.0 on ha id 3 anywhere. Could someone please explain what's going on here? Thanks much.
Dave
Stephen Lasseter wrote:
Fri Nov 19 00:00:01 GMT [smith: statd]: 12:00am up 25 days, 2:48 169239880 NFS ops, 0 CIFS ops, 63 HTTP ops Fri Nov 19 01:00:01 GMT [smith: statd]: 1:00am up 25 days, 3:48 169345577 NFS ops, 0 CIFS ops, 63 HTTP ops Fri Nov 19 02:00:01 GMT [smith: statd]: 2:00am up 25 days, 4:48 169451567 NFS ops, 0 CIFS ops, 63 HTTP ops Fri Nov 19 02:20:08 GMT [smith: isp_timeout]: 6.0(0xfffffc0000e84180): command timeout, retrying request Fri Nov 19 02:20:08 GMT [smith: isp_timeout]: Resetting SCSI bus 6 (ha #3) Fri Nov 19 02:25:34 GMT [smith: isp_timeout]: 6.0(0xfffffc0000e84660): command timeout, retrying request Fri Nov 19 02:25:34 GMT [smith: isp_timeout]: Resetting SCSI bus 6 (ha #3) Fri Nov 19 02:32:05 GMT [smith: rc]: de_main: e0 : Link up. Fri Nov 19 02:32:05 GMT [smith: rc]: relog syslog Fri Nov 19 02:30:53 GMT [smith: isp_timeout]: 6.0(0xfffffc0000e84b40): command timeout, retrying request
Fri Nov 19 02:32:05 GMT [smith: rc]: relog syslog SCSI drive 6.0 max timeout count exceeded - system resetting to recover!
Fri Nov 19 02:32:05 GMT [smith: rc]: NetApp Release 5.2.1P2 boot complete. Last disk update written at Fri Nov 19 02:30:22 GMT 1999
smith> sysconfig -r Volume brs1
RAID group 0
RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks)
parity 0a.8 0a 1 0 FC:A 17000/34816000 17366/35566480 data 0a.1 0a 0 1 FC:A 17000/34816000 17366/35566480 data 0a.4 0a 0 4 FC:A 17000/34816000 17366/35566480 data 0a.0 0a 0 0 FC:A 17000/34816000 17366/35566480 data 0a.5 0a 0 5 FC:A 17000/34816000 17366/35566480 data 0a.13 0a 1 5 FC:A 17000/34816000 17366/35566480 data 0a.10 0a 1 2 FC:A 17000/34816000 17366/35566480 data 0a.3 0a 0 3 FC:A 17000/34816000 17366/35566480 data 0a.11 0a 1 3 FC:A 17000/34816000 17366/35566480 data 0a.9 0a 1 1 FC:A 17000/34816000 17366/35566480 data 0a.2 0a 0 2 FC:A 17000/34816000 17366/35566480 data 0a.28 0a 3 4 FC:A 17000/34816000 17366/35566480 data 0a.29 0a 3 5 FC:A 17000/34816000 17366/35566480 data 0a.30 0a 3 6 FC:A 17000/34816000 17366/35566480
Volume spool (root)
RAID group 0
RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks)
parity 0a.12 0a 1 4 FC:A 17000/34816000 17366/35566480 data 0a.14 0a 1 6 FC:A 17000/34816000 17366/35566480 data 0a.6 0a 0 6 FC:A 17000/34816000 17366/35566480
Volume inbox
RAID group 0
RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks)
parity 0a.17 0a 2 1 FC:A 17000/34816000 17366/35566480 data 0a.16 0a 2 0 FC:A 17000/34816000 17366/35566480 data 0a.18 0a 2 2 FC:A 17000/34816000 17366/35566480 data 0a.21 0a 2 5 FC:A 17000/34816000 17366/35566480 data 0a.22 0a 2 6 FC:A 17000/34816000 17366/35566480 data 0a.24 0a 3 0 FC:A 17000/34816000 17366/35566480 data 0a.25 0a 3 1 FC:A 17000/34816000 17366/35566480
Volume hostapp
0a 1 4 FC:A 17000/34816000 17366/35566480 data 0a.14 0a 1 6 FC:A 17000/34816000 17366/35566480 data 0a.6 0a 0 6 FC:A 17000/34816000 17366/35566480
Volume inbox
RAID group 0
RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks)
parity 0a.17 0a 2 1 FC:A 17000/34816000 17366/35566480 data 0a.16 0a 2 0 FC:A 17000/34816000 17366/35566480 data 0a.18 0a 2 2 FC:A 17000/34816000 17366/35566480 data 0a.21 0a 2 5 FC:A 17000/34816000 17366/35566480 data 0a.22 0a 2 6 FC:A 17000/34816000 17366/35566480 data 0a.24 0a 3 0 FC:A 17000/34816000 17366/35566480 data 0a.25 0a 3 1 FC:A 17000/34816000 17366/35566480
Volume hostapp
RAID group 0
RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks)
parity 0a.20 0a 2 4 FC:A 17000/34816000 17366/35566480 data 0a.19 0a 2 3 FC:A 17000/34816000 17366/35566480
Spare disks
RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks)
spare 0a.27 0a 3 3 FC:A 0 17366/35566480 spare 0a.26 0a 3 2 FC:A 0 17366/35566480
Partner disks
RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks)
partner 1.0 1 0 0 FC:B 0 17366/35566480 partner 1.1 1 0 1 FC:B 0 17366/35566480 partner 1.2 1 0 2 FC:B 0 17366/35566480 partner 1.3 1 0 3 FC:B 0 17366/35566480 partner 1.4 1 0 4 FC:B 0 17366/35566480 partner 1.5 1 0 5 FC:B 0 17366/35566480 partner 1.6 1 0 6 FC:B 0 17366/35566480 partner 1.8 1 1 0 FC:B 0 17366/35566480 partner 1.9 1 1 1 FC:B 0 17366/35566480 partner 1.10 1 1 2 FC:B 0 17366/35566480 partner 1.11 1 1 3 FC:B 0 17366/35566480 partner 1.12 1 1 4 FC:B 0 17366/35566480 partner 1.13 1 1 5 FC:B 0 17366/35566480 partner 1.18 1 2 2 FC:B 0 17366/35566480 partner 1.19 1 2 3 FC:B 0 17366/35566480 partner 1.20 1 2 4 FC:B 0 17366/35566480 partner 1.14 1 1 6 FC:B 0 17366/35566480 partner 1.16 1 2 0 FC:B 0 17366/35566480 partner 1.17 1 2 1 FC:B 0 17366/35566480 partner 1.22 1 2 6 FC:B 0 17366/35566480 partner 1.21 1 2 5 FC:B 0 17366/35566480 partner 1.32 1 4 0 FC:B 0 17366/35566480 partner 1.33 1 4 1 FC:B 0 17366/35566480 partner 1.34 1 4 2 FC:B 0 17366/35566480 partner 1.35 1 4 3 FC:B 0 17366/35566480 partner 1.36 1 4 4 FC:B 0 17366/35566480 partner 1.37 1 4 5 FC:B 0 17366/35566480 partner 1.38 1 4 6 FC:B 0 17366/35566480 smith> -Steve
We see occasional SCSI timeouts on both our 740s with SCSI disks. The third 740 with FCAL disks doesn't seem to have the problem.
We replaced one disk which seemed to be causing the timeouts but then the fault moved to a different disk. I wonder if the timout period is too short. The errors only ever seem to happen in the middle of the night during a disk scrub.
I've just reported the problem again.
Dave Atkin
------------------------------------------------------ Dave Atkin, Head of Technical Services Computing Service, University of York, YORK YO10 5DD Phone: +44-1904-433804 (ddi) Fax: +44-1904-433740 Email: D.Atkin@york.ac.uk ------------------------------------------------------