From: Christophe Varoqui <christophe.varoqui@free.fr>
To: egoggin@vmware.com
Cc: dm-devel@redhat.com
Subject: RE: Re: multipathing pending issues with rhel
Date: Thu, 27 Nov 2008 23:16:25 +0100 [thread overview]
Message-ID: <20081127231625.69b450e0@plop> (raw)
> I think I inadvertantly made this matter worse about two years ago
> when I changed the clariion path checker to issue a scsi read via
> sg_read in libsg.c after inquiry page 0xc0 in order to discern an
> inactive from an active clariion snapshot logical unit. This change
> to multipath-tools/libcheckers/emc_clariion.c causes a path check on
> a path to incur a reservation error if the reservation is held
> by a different I/T nexus.
>
> A reasonable fix for this problem is to have sg_read in
> multipath-tools/libcheckers/libsg.c return PATH_UP even if the
> return value from ioctl is < 0 if the returned scsi status
> in io_hdr.status is SAM_STAT_RESERVATION_CONFLICT.
>
I recently tried an upstream kernel with the device handlers
infrastructure, and it seems the kernel rightfully drops the io on
reservation conflicts ... with due message in the logs, and returning a
success to the devmapper. No queueing, no retry, no problem.
I'll have to do some more testing to convince myself, but in the mean
time :
1/ Do you confirm my observations ?
2/ Does the Clariion snapshot still need your suggested fix in this new
context ? If so, would you care to submit a patch ?
Thanks for the comment,
cvaroqui
next reply other threads:[~2008-11-27 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-27 22:16 Christophe Varoqui [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-08 21:07 multipathing pending issues with rhel Christophe Varoqui
2008-10-08 22:11 ` Benjamin Marzinski
2008-10-08 23:06 ` Christophe Varoqui
2008-11-26 20:13 ` Edward Goggin
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=20081127231625.69b450e0@plop \
--to=christophe.varoqui@free.fr \
--cc=dm-devel@redhat.com \
--cc=egoggin@vmware.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 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.