From: "Ewan D. Milne" <emilne@redhat.com>
To: jthumshirn <jthumshirn@suse.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
Hannes Reinecke <hare@suse.de>,
Christoph Hellwig <hch@infradead.org>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Update SCSI target removal path
Date: Wed, 30 Mar 2016 12:30:27 -0400 [thread overview]
Message-ID: <1459355427.30035.28.camel@localhost.localdomain> (raw)
In-Reply-To: <da1b6206f0fba95e252e952a3afa07a6@suse.de>
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 <emilne@redhat.com> 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
next prev parent reply other threads:[~2016-03-30 16:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 7:09 [RESEND PATCH v2 0/2] Update SCSI target removal path Johannes Thumshirn
2016-03-30 7:09 ` [RESEND PATCH v2 1/2] Revert "scsi: fix soft lockup in scsi_remove_target() on module removal" Johannes Thumshirn
2016-03-30 7:09 ` Johannes Thumshirn
2016-03-30 7:09 ` [RESEND PATCH v2 2/2] scsi: Add intermediate STARGET_REMOVE state to scsi_target_state Johannes Thumshirn
2016-03-30 7:09 ` Johannes Thumshirn
2016-03-30 21:44 ` Sebastian Herbszt
2016-03-31 7:24 ` jthumshirn
[not found] ` <1459261538.30035.12.camel@localhost.localdomain>
[not found] ` <yq1twjorday.fsf@sermon.lab.mkp.net>
2016-03-30 11:01 ` [PATCH v2 0/2] Update SCSI target removal path jthumshirn
2016-03-30 16:30 ` Ewan D. Milne [this message]
2016-03-30 17:09 ` Laurence Oberman
[not found] ` <1d6331c085cbf189b2ead0baf92646068768c81c.1459249252.git.jthumshirn@suse.de>
2016-03-30 16:23 ` [RESEND PATCH v2 1/2] Revert "scsi: fix soft lockup in scsi_remove_target() on module removal" Ewan D. Milne
[not found] ` <108843b606da2c793bd830af42d5907bf8776d13.1459249252.git.jthumshirn@suse.de>
2016-03-30 16:25 ` [RESEND PATCH v2 2/2] scsi: Add intermediate STARGET_REMOVE state to scsi_target_state Ewan D. Milne
2016-03-30 16:43 ` [RESEND PATCH v2 0/2] Update SCSI target removal path James Bottomley
2016-03-31 6:58 ` jthumshirn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1459355427.30035.28.camel@localhost.localdomain \
--to=emilne@redhat.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=jthumshirn@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox