From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Ewan D. Milne" Subject: Re: [PATCH v2 0/2] Update SCSI target removal path Date: Wed, 30 Mar 2016 12:30:27 -0400 Message-ID: <1459355427.30035.28.camel@localhost.localdomain> References: <1459261538.30035.12.camel@localhost.localdomain> Reply-To: emilne@redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from mx1.redhat.com ([209.132.183.28]:41713 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755098AbcC3Qa3 (ORCPT ); Wed, 30 Mar 2016 12:30:29 -0400 In-Reply-To: Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: jthumshirn Cc: "Martin K. Petersen" , "James E.J. Bottomley" , Hannes Reinecke , Christoph Hellwig , linux-scsi@vger.kernel.org On Wed, 2016-03-30 at 13:01 +0200, jthumshirn wrote: > [+Cc linux-scsi back] > On 2016-03-30 02:59, Martin K. Petersen wrote: > >>>>>> "Ewan" == Ewan D Milne writes: > > > > Ewan> I would probably use an APCON or other physical layer switch to > > Ewan> drop the FC link and test the error recovery/device loss. But we > > Ewan> don't have one. > > > > They go for a couple of hundred bucks on eBay. I had one of these in a > > previous life and it was awesome. > > Though this would work (like any other FC/FCoE switch) I thought more of > a simulated environment. scsi_debug, Qemu, something like that. You might be able to do something with that but it doesn't quite do the same thing in terms of how a HBA/driver will react to a fault. You also need to be sure there is enough entropy in the timing of when the target goes away. (Otherwise, you could just rmmod scsi_debug...) > > I've had a look at scsi_debug but it seems like it's quite some > refactoring needed to get it to a point where one can simulate target > errors. I kinda like the idea of having something in > tools/testing/selftest but it'll probably end up with a FC switch. > > Johannes