From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: dm-devel@redhat.com, James Bottomley <James.Bottomley@suse.de>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: dm mpath: integrity errors should not cause failover
Date: Mon, 28 Mar 2011 20:13:28 -0400 [thread overview]
Message-ID: <yq14o6mkclz.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <20110328194831.GA29351@redhat.com> (Mike Snitzer's message of "Mon, 28 Mar 2011 15:48:32 -0400")
>>>>> "Mike" == Mike Snitzer <snitzer@redhat.com> writes:
Mike> Though this change could easily be considered a fix (for those
Mike> lucky enough to even have a DIF/DIX capable mpath
Mike> configuration)...
Yeah, I actually fixed this in my tree as a result of a user bug report.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2011-03-29 0:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 19:37 [PATCH] dm mpath: integrity errors should not cause failover Mike Snitzer
2011-03-28 19:48 ` Mike Snitzer
2011-03-29 0:13 ` Martin K. Petersen [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=yq14o6mkclz.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@suse.de \
--cc=dm-devel@redhat.com \
--cc=snitzer@redhat.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