From: christophe varoqui <christophe.varoqui@free.fr>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: device-mapper development <dm-devel@redhat.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [multipath] SCSI device capacity mess
Date: Tue, 26 Oct 2004 23:46:26 +0200 [thread overview]
Message-ID: <1098827186.4914.34.camel@zezette> (raw)
In-Reply-To: <1098826481.2140.534.camel@mulgrave>
Le mardi 26 octobre 2004 à 17:34 -0400, James Bottomley a écrit :
> On Tue, 2004-10-26 at 19:27, christophe varoqui wrote:
> > 1) make the /sys/block/*/size attribute writable
> > 2) resurrect a BLKSETSIZE ioctl
> > 3) make device-mapper less strict, and hope we can fix the size by a
> > device rescan when it get activated
> > 4) sell the culprit hardware
>
> Only 3 & 4 look viable. There's little point introducing an extra API
> or ioctl specifically to defeat a check, since the check will now be
> useless anyway.
>
:) I feared you would vote for 4)
That is not that viable for me, as you can imagine.
The culprit hardware, should I have reported, is a HSG80 controler pair
configured in multibus mode.
I though you could have considered 1) as it is just another way for root
to shoot itself and the multipath daemon can apply to detected valid
size on other paths to apply it to ghost paths. That didn't seem so
awkward to me.
I fear Alasdair reaction to 3) will be cold ... I still hope we can come
out with a solution, even one I havn't thought about.
> The "random" value is 1GB by the way. Since the dawn of time SCSI has
> reported this for devices that failed read capacity.
>
Ah, good to know. Thanks
regards,
--
christophe varoqui <christophe.varoqui@free.fr>
-
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
next prev parent reply other threads:[~2004-10-26 21:46 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 [this message]
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
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=1098827186.4914.34.camel@zezette \
--to=christophe.varoqui@free.fr \
--cc=James.Bottomley@SteelEye.com \
--cc=dm-devel@redhat.com \
--cc=linux-scsi@vger.kernel.org \
/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