From: Kipp Aldrich <kippa@tributary.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Error handling on FC devices
Date: Tue, 4 Dec 2012 09:56:55 -0600 [thread overview]
Message-ID: <50BE1D47.5020903@tributary.com> (raw)
In-Reply-To: <94D0CD8314A33A4D9D801C0FE68B40294CD03A65@G9W0745.americas.hpqcorp.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/03/2012 04:52 PM, Elliott, Robert (Server Storage) wrote:
>
>> Well, looking at QLogic and Emulex both emulate a bus reset with a
>> loop over each target and invoke a target reset there.
>> I somewhat fail to see the rationale behind it, other than emulating
>> the bus reset behaviour on SPI.
>> Given that the original target reset already failed (otherwise we
>> wouldn't be doing a bus reset), I doubt a _second_ target reset
>> will lead to a different result.
>>
>> So invoking REMOVE I_T NEXUS here can only improve matters :-)
>>
>> I'm all for renaming bus_reset, though :-)
>>
>
> Since modern storage fabrics don't really have a "bus" to reset any more, a bolder approach of getting rid of bus_reset might be warranted.
>
This is exactly what we do now. We modify drivers to disable bus_resets. It is dangerous, and disruptive, to reliable data storage,
especially on SANs. At least make it optional to enable it, disable it by default. Bus resets can destroy or lose customer data, for
goodness sake. Any commercial vendor using linux with these drivers that doesn't disable bus resets is risking their customer's data.
Really, how early '80s to have bus_reset. Time to move on.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
iEYEARECAAYFAlC+HUcACgkQeGqeAAwqIi147wCcDHEMmyr9m+umifJAbEDGns04
B4gAniGcrjM110cbX9/Ki/3e+jZO4d1o
=IRk4
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2012-12-04 16:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 12:41 Error handling on FC devices Hannes Reinecke
2012-11-26 22:32 ` James Smart
2012-11-27 20:03 ` Ewan Milne
2012-11-27 20:29 ` Elliott, Robert (Server Storage)
2012-11-28 7:09 ` Hannes Reinecke
2012-11-29 16:02 ` James Smart
2012-11-30 11:44 ` Hannes Reinecke
2012-11-30 16:54 ` Mike Christie
2012-12-03 7:15 ` Hannes Reinecke
2012-12-03 17:19 ` Jeremy Linton
2012-12-03 22:52 ` Elliott, Robert (Server Storage)
2012-12-04 15:56 ` Kipp Aldrich [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=50BE1D47.5020903@tributary.com \
--to=kippa@tributary.com \
--cc=linux-scsi@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.