From: Mike Snitzer <snitzer@redhat.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Heinz Mauelshagen <heinzm@redhat.com>,
dm-devel@redhat.com, Mikulas Patocka <mpatocka@redhat.com>,
"Alasdair G. Kergon" <agk@redhat.com>,
Zdenek Kabelac <zkabelac@redhat.com>
Subject: Re: dm-mirror: do not degrade the mirror on discard error
Date: Wed, 18 Feb 2015 13:21:19 -0500 [thread overview]
Message-ID: <20150218182119.GA3029@redhat.com> (raw)
In-Reply-To: <1424282047.2122.54.camel@HansenPartnership.com>
On Wed, Feb 18 2015 at 12:54pm -0500,
James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> On Wed, 2015-02-18 at 12:10 -0500, Mike Snitzer wrote:
> >
> > Let's please set this thread to one side. I already offered my thoughts
> > in this thread, see:
> > https://www.redhat.com/archives/dm-devel/2015-February/msg00076.html
> >
> > I'm not interested in wiring up the actual error return for dm-mirror's
> > benefit. If/when other dm-io consumers have a need to differentiate
> > between error codes we'll fix dm-io as needed.
>
> Yep, concur ... the point I've been obviously failing to make is that
> all the world is not an SSD.
I agree, and am aware. The layers that have needed to worry about
properly differentiating between these higher level returns from SCSI do
(e.g. dm-mpath). But it is pretty rare for bio-based DM targets to
differentiate between error codes. Not saying that is right, just that
is how things stand. Could be there is room for improvement in places.
prev parent reply other threads:[~2015-02-18 18:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 15:09 [PATCH] dm-mirror: do not degrade the mirror on discard error Mikulas Patocka
2015-02-12 15:43 ` Mikulas Patocka
2015-02-15 2:39 ` James Bottomley
2015-02-15 3:36 ` Mike Snitzer
2015-02-16 12:44 ` [PATCH] " Mikulas Patocka
2015-02-16 14:27 ` James Bottomley
2015-02-17 19:59 ` Mikulas Patocka
2015-02-18 15:16 ` James Bottomley
2015-02-18 16:29 ` Mikulas Patocka
2015-02-18 17:10 ` Mike Snitzer
2015-02-18 17:54 ` James Bottomley
2015-02-18 18:21 ` Mike Snitzer [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=20150218182119.GA3029@redhat.com \
--to=snitzer@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=heinzm@redhat.com \
--cc=mpatocka@redhat.com \
--cc=zkabelac@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 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.