Problem with mpt(4) and Infortrend RAID
Rong-En Fan
rafan at csie.org
Sat Feb 19 03:47:57 PST 2005
On Sat, Feb 19, 2005 at 06:28:46PM +0800, Xin LI wrote:
> Hi,
>
> ÔÚ 2005-02-19ÁùµÄ 18:12 +0800£¬Rong-En FanдµÀ£º
> > On Sat, Feb 19, 2005 at 05:45:12PM +0800, Xin LI wrote:
> > > Would you please try:
> > > camcontrol tags da1
> > >
> > > To see how many tags are actually allowed for the device, at the host
> > > side? It comes to my mind that:
> >
> > I have already done -N 32, I remembered that original is 25x.
>
> Er... Pardon... You mean you have already done this before you got the
> error message, or just have done that?
just have done that.
> > > Here: You have allowed only 32, and if the host has exceeded the
> > > limitation, then something strange *may* happen. My bet is to decrease
> >
> > I just found the Infortrend's manual, it says that if
> > hos exceeded this limit, the controller will not response
> > and host *might* reduce the # later. Hmm, it seems match
> > my situation.
>
> Yes, and this has generated problem for me, too. It should be good if
> there's someone can tell us how to obtain the maximum tag depth allowed
> by the infotrend device (I don't know if there is one, as I'm not a SCSI
> guru:-)
>
> > > the tags allowed at host side, to something like 32:
> > >
> > > camcontrol tags da1 -N 32.
> > >
> > > It's also possible to modify cam_xpt.c to set the default number.
> >
> > Hmm, seems ok for me. My system's disk is ips(4) which does not
> > use CAM layer. So, I can put camcontrol to rc.
>
> It's also possible to add the disk array quirk to the cam_xpt.c, too.
> But that's of course too hacky IMO :-)
Ya, I think so :)
Regards,
Rong-En fan
More information about the freebsd-scsi
mailing list