From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Date: Fri, 12 Aug 2005 15:33:09 +0000 Subject: Re: udev Message-Id: <42FCC135.7030506@ipunwired.com> List-Id: References: <20050811182850.GD15803@kroah.com> In-Reply-To: <20050811182850.GD15803@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org The main problem I was having is that when the system starts and all the=20 drives are there udev used my rules file and everything works. The=20 moment the system starts and say sdc is missing, it will read the file=20 and apply the rules for sda and sdb, but not apply it to any other the=20 drives from that point on. The default system takes over, so a drive=20 that I need to be sdd ends up being sdc. I had though about that, but wouldn't you have to regenerate the file=20 each time if there was a drive change? I figured the SCSI enumeration=20 would work the best, in the event of a fail the new drive can be plugged=20 in to the same particular channel and in be labeled correctly. I'll take=20 a look further in to the using the scsi_id thanks mike Kay Sievers wrote: > On Thu, Aug 11, 2005 at 03:21:15PM -0400, Mike wrote: >=20 >>running udev on each disk gave me >> >>[root@localhost udev-065]# udevtest /sys/block/sdb >>version 039 >>looking at '/block/sdb' >>configured rule in '/etc/udev/rules.d/10-udev.rules' at line 2 applied,=20 >>added >>symlink 'raid11' >>configured rule in '/etc/udev/rules.d/10-udev.rules' at line 2 applied,=20 >>'sdb' >>becomes '%k' >>creating device node '/dev/sdb', major =3D '8', minor =3D '16', mode =3D = >>'060660', uid >>=3D '0', gid =3D '6' >> >>for all the disk that were present. I removed sda before running the=20 >>test. The sda drive returns looking at /block/sda and dosn't go any furth= er. >=20 >=20 > I don't think that you can rely on the scsi enumeration to make stable > nodes, but I'm not entirely sure in your case. >=20 > Better try to read some persistent data from the drive itself like the > serial number. You may look at the persistent device naming rules: > http://kernel.org/git/gitweb.cgi?p=3Dlinux/hotplug/udev.git;a=3Dblob;h= =D208f5068df7c1b2e0c994c63489069af054b362;hb=D47fd445bd9ade720776f661a4ad7c= 4b2202d6f0;f=3Detc/udev/gentoo/udev.rules#l246 >=20 > and see if you can get unique properties from your drive with ata_id > or scsi_id. >=20 > Good luck, > Kay >=20 ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ 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