From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Christie Subject: Re: [PATCH RFC] replace dm hw handlers with scsi handlers Date: Wed, 18 Oct 2006 11:27:31 -0500 Message-ID: <453655F3.1020603@cs.wisc.edu> References: <1160684310.4163.4.camel@madmax> <4530E19A.8040002@cs.wisc.edu> <1161074225.6464.1.camel@localhost.localdomain> <20061018143324.GB25084@pentland.suse.de> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20061018143324.GB25084@pentland.suse.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Hannes Reinecke Cc: device-mapper development , linux-scsi@vger.kernel.org List-Id: linux-scsi@vger.kernel.org Hannes Reinecke wrote: > Hi Mike, >=20 > On Tue, Oct 17, 2006 at 10:37:05AM +0200, Christophe Varoqui wrote: >> Le samedi 14 octobre 2006 =C3=A0 09:09 -0400, Mike Christie a =C3=A9cr= it : >>> Christophe V, I was wondering what is the vendor/module info for your >>> box? We have a MSA1000 VOLUME/COMPAQ here, but START_STOP does not >>> work. >>> I mean if I send the command it always executes successfully, but the >>> device does not failover (READ/WRITEs fail). I tried just running >>> sg_start and this runs ok but READ/WRITE still fail, so I hacked up >>> scsi_debug to simulate my testing.=20 >> It was a HSG80 based array, namely a HP EMA8000. >> I do not have access to this hardware anymore. >> >=20 > Hmm. Finally I got a MSA1000 here, too (Thanks, HP!). dm_hp_sw seems > to work properly there. Note that according to the HP qla2xxx sources > the MSA1000 might take some time to actually do the switchover. > Appearently they return NOT_READY / UNIT_ATTENTION and some weird statu= s > in byte 12 & 13 of the sense buffer (!). So please check the sense code > if there is anything untoward. Will do. I wanted to see if the NOT_READY in scsi_error.c caught it but I guess it is not the same asc/asq. I will look at the qlogic driver for the values. Ditto for UNIT_ATTENTION. > Oh, and you can check whether the failover really occured by using > the management console; 'show this_controller' and 'show other_controll= er' > will tell you which one's active. > Drop me a mail if you got further questions.=20 >=20 Thanks for checking that out.