Date: Fri, 11 Aug 2006 15:43:48 +0000 From: Geoff Buckingham <geoffb@chuggalug.clues.com> To: Eric Anderson <anderson@centtech.com> Cc: freebsd-scsi@freebsd.org Subject: Re: isp issues on recent -STABLE Message-ID: <20060811154348.GA83765@chuggalug.clues.com> In-Reply-To: <44DC6F9F.4060405@centtech.com> References: <44DB8A9C.8090609@centtech.com> <44DC6F9F.4060405@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 11, 2006 at 06:53:03AM -0500, Eric Anderson wrote: > [..snip..] > Aug 9 23:02:10 snapshot1 kernel: isp0: command timed out for 0.2.2 > Aug 9 23:02:10 snapshot1 kernel: (da8:isp0:0:2:2): Command timed out > Aug 9 23:02:10 snapshot1 kernel: (da8:isp0:0:2:2): Retrying Command > Aug 9 23:26:58 snapshot1 kernel: (da3:isp0:0:1:0): Queue Full > Aug 9 23:26:58 snapshot1 kernel: (da3:isp0:0:1:0): tagged openings now 254 I don't what may have changed in the driver recently, but from your post you seem to be using the FC isp and potentially a "SAN" presenting arrays as luns to you rather than JBOD on a loop or switch. If you you have some kind of data mover presenting arrays, your SAN vendor may well recomend a maximum queue size per lun (often 20-30) man camcontrol, look at the tags section. Your commands may be timing out because you have managed to queue too many command (which I hope should not happen). Or..... Your queues could be filling because your commands are timing out. Which would imply something is broke :-(
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060811154348.GA83765>