From: Christophe Varoqui <christophe.varoqui@free.fr>
To: linux-hotplug@vger.kernel.org
Subject: Re: Bug#351606: [shuey@fmepnet.org: Re: Bug#351606: multipath
Date: Thu, 09 Feb 2006 20:00:11 +0000 [thread overview]
Message-ID: <1139515211.2915.21.camel@zezette> (raw)
On jeu, 2006-02-09 at 20:28 +0100, Kay Sievers wrote:
> On Thu, Feb 09, 2006 at 08:25:14PM +0100, Bastian Blank wrote:
> > Hi folks
> >
> > I got the following bugreport against multipath-tools, which by default
> > uses scsi_id to detect multiple paths.
> >
> > scsi_id on SATA devices (via libata) returns a string like:
> > | 0ATA_ST3160827AS_Linux_ATA-SCSI_simulator
>
> Add this:
> $ cat /etc/scsi_id.config
> vendor="ATA",options=-p 0x80
>
In this bug's context the following should work too,
in /etc/multipath.conf :
devices {
device {
vendor ATA
product *
getuid_callout "/sbin/scsi_id -g -u -p 0x80 -s /block/%n"
}
}
Now, it'll likely not solve all problems. I guess what is really wanted
is multipath to blacklist the SATA devices. This feature is in the devel
branch only.
blacklist {
device {
vendor ATA
product *
}
}
Regards,
cvaroqui
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
reply other threads:[~2006-02-09 20:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1139515211.2915.21.camel@zezette \
--to=christophe.varoqui@free.fr \
--cc=linux-hotplug@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 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.