public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurence Oberman <loberman@redhat.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>,
	Lukas Herbolt <lherbolt@redhat.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Fwd: All scsi_debug devices in the scsi_debug driver share the same RAM space
Date: Wed, 14 Feb 2018 13:45:20 -0500	[thread overview]
Message-ID: <1518633920.11799.1.camel@redhat.com> (raw)
In-Reply-To: <yq11shoqpuy.fsf@oracle.com>

On Tue, 2018-02-13 at 21:14 -0500, Martin K. Petersen wrote:
> Lukas,
> 
> > I like the idea to have an option to separate the memory area for
> > different LUNs, while keeping the current behavior as default.
> 
> As the name implies, scsi_debug is mostly a tool for debugging the
> SCSI
> stack.
> 
> If you care about storing data, why not simply use target in loopback
> mode?
> 

Hi Martin

I think what Lukas was really looking for is what I started out
wanting.
Individual devices that could be put into configurations such as md-
raid for testing and could be used with fault injection.

In the end I had to use 5 (LIO or physical) devices and 1 scsi_debug
device to reproduce an issue for md-raid.
Target loopback was an option too.

I have fault injection in qla2xxx tcm already but not in the target
core.

I guess it time i look into that now so will proceed with that.

Regards
Laurence

      reply	other threads:[~2018-02-14 18:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-03 19:43 All scsi_debug devices in the scsi_debug driver share the same RAM space Laurence Oberman
2018-02-05 14:32 ` Laurence Oberman
     [not found]   ` <CAM4Jq_43+JrSTvXsq7kgRLikqHb2iwFMYKTBuQjQ5h2Dn1ka+A@mail.gmail.com>
2018-02-12 15:04     ` Fwd: " Lukas Herbolt
2018-02-14  2:14       ` Martin K. Petersen
2018-02-14 18:45         ` Laurence Oberman [this message]

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=1518633920.11799.1.camel@redhat.com \
    --to=loberman@redhat.com \
    --cc=lherbolt@redhat.com \
    --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