public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: James Bottomley <James.Bottomley@suse.de>
Cc: Hannes Reinecke <hare@suse.de>,
	dgilbert@interlog.com, James Bottomley <jbottomley@suse.de>,
	linux-scsi@vger.kernel.org, jaxboe@fusionio.com,
	michaelc@cs.wisc.edu, agk@redhat.com
Subject: Re: [PATCH v4 1/3] scsi: Detailed I/O errors
Date: Thu, 27 Jan 2011 17:54:31 -0500	[thread overview]
Message-ID: <20110127225431.GI14951@redhat.com> (raw)
In-Reply-To: <1296168102.3050.83.camel@mulgrave.site>

On Thu, Jan 27 2011 at  5:41pm -0500,
James Bottomley <James.Bottomley@suse.de> wrote:

> On Thu, 2011-01-27 at 17:35 -0500, Mike Snitzer wrote:
> > On Tue, Jan 18 2011 at  7:01am -0500,
> > Hannes Reinecke <hare@suse.de> wrote:
> > 
> > > On 01/18/2011 12:33 PM, Douglas Gilbert wrote:
> > > 
> > > This patchset is primarily for fixing up multipathing,
> > > which has the habit of retrying failed I/Os on the
> > > next path. For some errors this is just pointless
> > > (eg MEDIUM ERROR), for some errors this is the desired
> > > behaviour (namely transport errors), and for others
> > > this is positively damaging (persistent reservation
> > > failures).
> > > Just plain EIO simply don't cover the whole range :-)
> > > 
> > > > 
> > > > BTW might "vulgo" be "ergo" [Latin: therefore]?
> > > > 
> > > Nope. Correct etymology is from 'sermo vulgaris',
> > > ie the language of the common people.
> > > But maybe I should remove it for the next
> > > round to avoid confusion.
> > 
> > Is a new round even needed given there haven't been any code issues
> > raised against v4?
> > 
> > James, what are your thoughts on this patchset?  Would be great to get
> > this in scsi-misc for 2.6.39
> > 
> > Please advise,
> 
> Well, it covers three subsystems ... I was waiting for Alasdair and Jens
> to ack ... but I bet they each were waiting for the other two to ack ...
> 
> So, I'll take it if no objections.

OK, I just sent a mail to jens and alasdair asking the same ;)

Thanks,
Mike

  reply	other threads:[~2011-01-27 22:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18  9:13 [PATCH v4 0/3] differentiate between I/O errors Hannes Reinecke
2011-01-18  9:13 ` [PATCH v4 1/3] scsi: Detailed " Hannes Reinecke
2011-01-18 11:33   ` Douglas Gilbert
2011-01-18 12:01     ` Hannes Reinecke
2011-01-27 22:35       ` Mike Snitzer
2011-01-27 22:41         ` James Bottomley
2011-01-27 22:54           ` Mike Snitzer [this message]
2011-01-28  8:12             ` Jens Axboe
2011-01-28 13:11           ` Alasdair G Kergon
2011-01-18  9:13 ` [PATCH v4 2/3] dm mpath: propagate target errors immediately Hannes Reinecke
2011-01-18  9:13 ` [PATCH v4 3/3] block: improve detail in I/O error messages Hannes Reinecke
2011-01-27 22:51   ` Mike Snitzer

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=20110127225431.GI14951@redhat.com \
    --to=snitzer@redhat.com \
    --cc=James.Bottomley@suse.de \
    --cc=agk@redhat.com \
    --cc=dgilbert@interlog.com \
    --cc=hare@suse.de \
    --cc=jaxboe@fusionio.com \
    --cc=jbottomley@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    /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