From: Tore Anderson <tore@linpro.no>
To: Michael Loehr <MLOEHR@de.ibm.com>
Cc: Linux SCSI Mailing List <linux-scsi@vger.kernel.org>,
mdr@sgi.com, hch@infradead.org, James.Smart@Emulex.Com
Subject: Re: Disabling dev_loss_tmo?
Date: Tue, 13 Nov 2007 12:07:48 +0100 [thread overview]
Message-ID: <47398584.6010407@linpro.no> (raw)
In-Reply-To: <OF50F972F5.7F1838AD-ONC1257392.0038C0B2-C1257392.003926A2@de.ibm.com>
* Michael Loehr
> in recent SLES10 kernels the additional setting "remove_on_dev_loss" allows
> to control, if the devices are removed or not. Unfortunately this change
> did not find its way upstream yet ...
Thanks for pointing this out. I found that this patch was submitted
here over a year ago, but unfortunately was rejected:
http://www.spinics.net/lists/linux-scsi/msg10289.html (I'm adding Cc's
to the folks that posted to that thread)
Christoph, would you be inclined to reconsider your position on this
patch if it was changed so that the default behaviour would still be to
remove devices after dev_loss_tmo expired?
The current behaviour is causing troubles because of intermittent rport
unavailability and the subsequent remove/readd actions way more often
than I am permanently removing targets from my SAN, so for me being able
to disable the automatic device removal would be a huge improvement for
me (and I doubt I'm the only one that feels this way).
Regards
--
Tore Anderson
next prev parent reply other threads:[~2007-11-13 11:07 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 [this message]
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
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=47398584.6010407@linpro.no \
--to=tore@linpro.no \
--cc=James.Smart@Emulex.Com \
--cc=MLOEHR@de.ibm.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