public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Smart <James.Smart@Emulex.Com>
Cc: Linux SCSI Mailing List <linux-scsi@vger.kernel.org>,
	Christoph Hellwig <hch@infradead.org>,
	device-mapper development <dm-devel@redhat.com>,
	MLOEHR@de.ibm.com, Michael Reed <mdr@sgi.com>
Subject: Re: Disabling dev_loss_tmo?
Date: Wed, 14 Nov 2007 14:00:04 -0500	[thread overview]
Message-ID: <473B45B4.3010708@emulex.com> (raw)
In-Reply-To: <473B1692.8050606@linpro.no>

I've added the dm reflector to this email...

> Best would to have DM-multipath handle the disconnects gracefully, of
> course.  But since it doesn't appear to be happening anytime soon:  A
> workaround provided by the transport layer would be very welcome!  I
> don't use iSCSI or SAS with DM so I don't know if such a workaround is
> wanted there too, but with FC it is necessary.  Even if it is a bad
> approach it is much better than nothing, the way I see it.

Background of where this thread started is:
http://marc.info/?l=linux-scsi&m=119494675103771&w=2

Can someone from the DM community comment on where things are, or are
going, for handling disconnects w/ device teardown ??

-- james s

  reply	other threads:[~2007-11-14 19:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13  9:11 Disabling dev_loss_tmo? Tore Anderson
2007-11-13 10:24 ` Michael Loehr
2007-11-13 11:07   ` Tore Anderson
2007-11-13 16:18 ` James Smart
2007-11-14  8:10   ` Tore Anderson
2007-11-14 14:29     ` James Smart
2007-11-14 15:38       ` Tore Anderson
2007-11-14 19:00         ` James Smart [this message]
2007-11-15  8:02           ` [dm-devel] " Mike Anderson

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=473B45B4.3010708@emulex.com \
    --to=james.smart@emulex.com \
    --cc=MLOEHR@de.ibm.com \
    --cc=dm-devel@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mdr@sgi.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