linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gerald V. Livingston II" <gerald.hotplug@sysmatrix.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Statically nameing a SCSI device
Date: Wed, 15 Aug 2007 22:16:40 +0000	[thread overview]
Message-ID: <4892.65.170.133.237.1187216200.squirrel@webmail.sysmatrix.net> (raw)
In-Reply-To: <1240.65.170.133.237.1186867534.squirrel@webmail.sysmatrix.net>

On Sun, August 12, 2007 11:58, Gerald V. Livingston II said:
> On Sun, August 12, 2007 11:29, Kay Sievers said:
>> On 8/12/07, Gerald V. Livingston II <gerald.hotplug@sysmatrix.net>
>> wrote:
>>> The disks will all be the same model so the info in /dev/disk will be
>>> the
>>> same except for a number or two. Too easy to mix them up if I'm looking
>>> for something specific while moving hardware around.
>>
>> If you use rules later than 60-*.rules, ENV{ID_SERIAL} is already set
>> by udev's persistent rules, and there is no need to run scsi_id again.
>>
>> Kay
>
> On my Debian system install persistent.rules runs at "z20" so I've moved
> my SATA rules file to z22_my.sata.rules.
>
> Since nothing on the SYSTEM (only my brain) seems to require /dev/sd"x" to
> be static I've also changed the persistent symlinks to be more descriptive
> for me. The z22_my.sata.rules file is currently a single line:
>
> KERNEL="sd*[!0-9]",
> ENV{ID_SERIAL}="SATA_WDC_WD2500YS-01_WD-WCANY1955037", SYMLINK+="sata1"
>

This works great. Wherever the SATA drive end up in the chain it gets
linked as /dev/sata1.

But, my brain is missing something else. I am doing LVM on these disks but
not "whole device" LVM, so, I also need symlinks for /dev/sdd1 etc to be
created as /dev/sata1_1, /dev/sata1_2, etc.

Never mind, I got it. But I'll post this for the archives anyway:

My SATA rules file (which runs AFTER the stock "persistent.rules" file) is
now two line for the single drive I have installed. Other lines will be
added for each drive I install later to link them to sata2 etc.

KERNEL="sd*[!0-9]",
ENV{ID_SERIAL}="SATA_WDC_WD2500YS-01_WD-WCANY1955037", SYMLINK+="sata1"

KERNEL="sd*[0-9]",
ENV{ID_SERIAL}="SATA_WDC_WD2500YS-01_WD-WCANY1955037",
SYMLINK+="sata1_%n"

Gerald


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
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

      parent reply	other threads:[~2007-08-15 22:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-11 21:25 Statically nameing a SCSI device gerald.hotplug
2007-08-12  3:49 ` Greg KH
2007-08-12  5:50 ` Andrey Borzenkov
2007-08-12  8:16 ` gerald.hotplug
2007-08-12 12:24 ` Kay Sievers
2007-08-12 12:43 ` Andrey Borzenkov
2007-08-12 13:00 ` Kay Sievers
2007-08-12 15:46 ` Gerald V. Livingston II
2007-08-12 16:29 ` Kay Sievers
2007-08-12 16:58 ` Gerald V. Livingston II
2007-08-15 22:16 ` Gerald V. Livingston II [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=4892.65.170.133.237.1187216200.squirrel@webmail.sysmatrix.net \
    --to=gerald.hotplug@sysmatrix.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).