Date: Mon, 24 Apr 2000 23:09:47 +0200 From: sthaug@nethelp.no To: mjacob@feral.com Cc: ken@kdm.org, freebsd-scsi@FreeBSD.ORG Subject: Re: Safe mounting of one file system on multiple hosts? Message-ID: <76384.956610587@verdi.nethelp.no> In-Reply-To: Your message of "Mon, 24 Apr 2000 13:58:33 -0700 (PDT)" References: <Pine.BSF.4.05.10004241358120.87772-100000@semuta.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Huh, well, this looks more like a problem with the target than anything else,
> but it's hard to say.
Possibly so - but:
- Several people have suggested that CMD RAID controllers do indeed have
problems with multiple LUN support,
- I experience this problem only on the host channel with multiple LUNs,
- The fix suggested by Oliver Blasnik (see below) seems to work.
All of this makes me conclude that the problem probably *is* due to bugs
in the multiple LUN support in the CMD firmware.
Steinar Haug, Nethelp consulting, sthaug@nethelp.no
----------------------------------------------------------------------
From: "Oliver Blasnik" <ob@omnilink.net>
To: "Kenneth D. Merry" <ken@kdm.org>,
"LukeUnix" <lukeunix@infosite.com>
Cc: <freebsd-scsi@FreeBSD.ORG>
References: <200001251721.JAA32558@infosite.com> <20000125131901.A96487@panzer.kdm.org>
Subject: Re: CMD problems
Date: Thu, 27 Jan 2000 12:14:02 +0100
Organization: Omnilink ISC
Hi there,
Luke had some (well known) Problems:
> > I am having problems with a CMD CRD-5440 with multiple luns. The
config is 2
> > /kernel: (da2:ahc1:0:1:0): SCB 0x18 - timed out while idle, LASTPHASE
==
> > 0x1, SEQADDR == 0xa
> > /kernel: (da2:ahc1:0:1:0): Queuing a BDR SCB
> > /kernel: (da2:ahc1:0:1:0): Bus Device Reset Message Sent
> > /kernel: (da2:ahc1:0:1:0): no longer in timeout, status = 34b
> > /kernel: ahc1: Bus Device Reset on A:1. 2 SCBs aborted
> > /kernel: (da2:ahc1:0:1:0): SCB 0x28 - timed out while idle, LASTPHASE
==
> > 0x1, SEQADDR == 0x9
Go into CMD-Setup via serial, disable "Tagged Queuing" on the/all
Host-Channels.
Kenneth stated:
> The short answer is "don't do that".
> Other folks have discovered that the CMD RAID arrays don't quite work
right
> with more than one LUN enabled.
> Sorry I can't provide any solutions here, but this is almost certainly a
> problem with CMD's firmware, and the workaround is to only use one LUN
on
> the controller.
True, the problem is that crappy firmware, which does not currectly share
the commandqueue between multiple LUNs. If you _need_ multiple LUNs per
Hostchannel, disable tagged queuing.
This slows down disk-i/o a little bit, but the CMD works out very well due
to the fast cache-access.
Cu, Oliver
--
__ OMNILINK Internet Service Center GmbH
/ \ Hahnstrasse 70, 60528 Frankfurt
__\ /_________ Tel.: (0 69)66 44 10 Fax: (0 69)66 44 11 99
O M N I L I N K http://www.omnilink.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?76384.956610587>