From: gerald.hotplug@sysmatrix.net
To: linux-hotplug@vger.kernel.org
Subject: Re: Statically nameing a SCSI device
Date: Sun, 12 Aug 2007 08:16:21 +0000 [thread overview]
Message-ID: <3934.65.170.133.237.1186906581.squirrel@webmail.sysmatrix.net> (raw)
In-Reply-To: <1240.65.170.133.237.1186867534.squirrel@webmail.sysmatrix.net>
> On Sunday 12 August 2007, gerald.hotplug@sysmatrix.net wrote:
>> These drives are for data storage only but they will probably be
>> formatted
>> using LVM so I can create one big mount point without having a symlink
>> farm growing so I need to keep stable /dev/sd'x' names for LVM to keep
>> track of them.
>>
>
> what makes you believe so?
Nothing at the moment. In setting up this "play system" (personal server
for mail, web, and multimedia) I suddenly find myself reading man pages
and tutorials for a lot more subsystems than my brain apparently has the
capacity to handle at one time.
Ive mixed up what requires which more than once in the last few days.
Now, that being said, it will be a lot easier for *ME* if I always know
exactly where the SATA drives are located in the plain-old /dev tree and
if I can call them /dev/sdw or /dev/sdz rather than
/dev/disk/by-id/ata-WDC_WD2500YS-01S-WD-WCANY1955037
I added this to my local.rules and udevtest says it works great for the
first drive I already have installed:
KERNEL="sd*[!0-9]", IMPORT="/sbin/scsi_id -g -x $tempnode"
KERNEL="sd*[!0-9]",
ENV{ID_SERIAL}="SATA_WDC_WD2500YS-01_WD-WCANY1955037", NAME="sdw"
As I add the other 3 drives I just need to add lines to identify their
serial numbers and set them at sdx, sdy, and sdz.
Thanks,
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
next prev parent reply other threads:[~2007-08-12 8: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 [this message]
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
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=3934.65.170.133.237.1186906581.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).