Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 12 Aug 2006 11:01:49 -0700
From:      "Matthew Jacob" <lydianconcepts@gmail.com>
To:        "Eric Anderson" <anderson@centtech.com>
Cc:        freebsd-scsi@freebsd.org
Subject:   Re: isp issues on recent -STABLE
Message-ID:  <7579f7fb0608121101g112e006cy1112d282fab753d3@mail.gmail.com>
In-Reply-To: <44DCA9F1.1000302@centtech.com>
References:  <44DB8A9C.8090609@centtech.com> <44DC6F9F.4060405@centtech.com> <20060811154348.GA83765@chuggalug.clues.com> <44DCA9F1.1000302@centtech.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hmm. I have no special help on this one. This doesn't seem
*particularly* related to any changes I've made recently.

If you could isolate a date/change when this occurred for you it would help.

All I see in the messages below is indications that we've given your
storage way too much work to do.

On 8/11/06, Eric Anderson <anderson@centtech.com> wrote:
> On 08/11/06 10:43, Geoff Buckingham wrote:
> > 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)
>
> I have this one host connected to a single QLogic fiber channel switch,
> which has 5 ACNC fiber channel arrays attached to it, along with a tape
> robot and tape drives.  Three of the arrays present 3 LUNs each (2TB per
> LUN), and two of them present 2 LUNs each, 4GB and 10TB - I'm not using
> these two arrays much yet, and are not really associated with the problems.
>
> > 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 :-(
>
> Strange that I've never hit this in the past, but now I seem to be
> hitting it quite often.  The vendor of the arrays says queue depth is
> 256 per LUN, and that coincides with my messages above I believe.
>
> Eric
>
>
>
> --
> ------------------------------------------------------------------------
> Eric Anderson        Sr. Systems Administrator        Centaur Technology
> Anything that works is better than anything that doesn't.
> ------------------------------------------------------------------------
> _______________________________________________
> freebsd-scsi@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-scsi
> To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org"
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7579f7fb0608121101g112e006cy1112d282fab753d3>