Date: Mon, 18 Oct 2004 20:18:29 +0200 From: "Kipp Holger" <h.kipp@eurowings.com> To: "Matthew Jacob" <mjacob44@yahoo.com>, <freebsd-scsi@freebsd.org> Subject: [SOLVED] RE: Interesting SCSI-Problem with Quantum Atlas10K3 (from freebsd-stable) Message-ID: <BA84A761ED41C54893BED691A4A574CF4061D4@EXCH5.eurowings.com>
next in thread | raw e-mail | index | archive | help
It was after all a defect disk drive (one of those three drives had an 'oscillating' writing performance (ie between 0 bytes/sec and maximum throughput) which gave all sorts of interesting behaviour within vinum as raid 5. This was very hard to debug under FreeBSD 4.10 and might explain why changing the available command queue length first looked like solving the problem... (because it changed the timing issues of the bad drive). Regards, Holger Kipp -----Original Message----- From: Matthew Jacob [mailto:mjacob44@yahoo.com] Sent: Wed 29.09.2004 22:12 To: Kipp Holger; freebsd-scsi@freebsd.org Cc:=09 Subject: Re: Interesting SCSI-Problem with Quantum Atlas10K3 (from = freebsd-stable) It's not a command queue length issue. The message indicates that we had a disk command timeout that when we turned around and called the interrupt service routine that the command did get serviced after all. You didn't say what kind of MPT h/w you're running on. =09 =09 __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BA84A761ED41C54893BED691A4A574CF4061D4>