All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.de>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: device-mapper development <dm-devel@redhat.com>,
	christophe varoqui <christophe.varoqui@free.fr>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [dm-devel] [multipath] SCSI device capacity mess
Date: Thu, 28 Oct 2004 20:21:54 +0200	[thread overview]
Message-ID: <20041028182154.GY32712@marowsky-bree.de> (raw)
In-Reply-To: <20041028181436.GA18874@beaverton.ibm.com>

On 2004-10-28T11:14:36, Patrick Mansfield <patmans@us.ibm.com> wrote:

> > Can't we do a test-unit-ready before trying to read and then just not
> > read the partition table w/o so much noise?
> We already issue a TUR in sd_spinup_disk() prior to the READ CAPACITY and
> partition reads.

I'm just saying we should stop on the first failed command (TUR) and not
retry to read all 64 sectors regardless. I can live with one error per
passive path, but 64 really kills the logs.


Sincerely,
    Lars Marowsky-Brée <lmb@suse.de>

-- 
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX AG - A Novell company

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2004-10-29 14:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-26 23:27 [multipath] SCSI device capacity mess christophe varoqui
2004-10-26 21:34 ` James Bottomley
2004-10-26 21:46   ` christophe varoqui
2004-10-27  8:17 ` [dm-devel] " Lars Marowsky-Bree
2004-10-27  8:42   ` Lars Marowsky-Bree
2004-10-27 18:51     ` Bryan Henderson
2004-10-29 14:12       ` Lars Marowsky-Bree
2004-10-29 16:48         ` Bryan Henderson
2004-10-27 19:02   ` christophe varoqui
2004-10-27 19:37     ` Eddie Williams
2004-10-27 20:19       ` christophe varoqui
2004-10-27 20:34         ` Greg Freemyer
2004-10-27 20:28     ` Philip R Auld
2004-10-27 21:57     ` James Bottomley
2004-10-28 11:37       ` Lars Marowsky-Bree
2004-10-28 18:14         ` Patrick Mansfield
2004-10-28 18:21           ` Lars Marowsky-Bree [this message]
2004-10-30  0:41             ` Patrick Mansfield
2004-10-30  1:01               ` Patrick Mansfield
2004-10-30  7:21               ` christophe varoqui
2004-10-30  8:22                 ` christophe varoqui
2004-11-02 15:23                 ` Lars Marowsky-Bree
2004-10-28 11:35     ` Lars Marowsky-Bree

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=20041028182154.GY32712@marowsky-bree.de \
    --to=lmb@suse.de \
    --cc=christophe.varoqui@free.fr \
    --cc=dm-devel@redhat.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=patmans@us.ibm.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.