From: Andreas Herrmann <aherrman@web.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi@vger.kernel.org, aherrman@de.ibm.com
Subject: Re: [PATCH 1/7] zfcp: introduce eh_timed_out handler
Date: Sun, 04 Sep 2005 12:49:03 +0200 [thread overview]
Message-ID: <431AD11F.1050903@web.de> (raw)
On Sat, Sep 03, 2005 at 14:53:00, Christoph Hellwig wrote:
> Please don't do this. We have proper midlayer handling (plus FC
> transport
> class wrappers) to handle that case without introducing a big mess in
> the
> driver. Please take a look at fc_remote_port_{block,unblock}
Thanks for that hint.
But does fc_remote_port_unblock set online devices that were
previously offlined?
If not the problem of offlined devises is not solved with
this. If zfcp would block requests if it detects a path error a scsi
request might have already send to the devise which might cause that
the devise if offlined. Now if zfcp detects the path is up again and
calls fc_remote_port_unblock the device can still not be used because
it is offline.
I'll have to check the code if I am back from vacation.
Regards,
Andreas
(PS: sorry for using this alternate email account)
next reply other threads:[~2005-09-04 10:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-04 10:49 Andreas Herrmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-04 10:37 [PATCH 1/7] zfcp: introduce eh_timed_out handler Andreas Herrmann
2005-09-04 10:34 Andreas Herrmann
2005-09-03 13:21 Andreas Herrmann
2005-09-03 12:30 Andreas Herrmann
2005-09-03 12:56 ` Arjan van de Ven
2005-09-03 13:45 ` James Bottomley
2005-09-03 14:53 ` Christoph Hellwig
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=431AD11F.1050903@web.de \
--to=aherrman@web.de \
--cc=aherrman@de.ibm.com \
--cc=hch@infradead.org \
--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.