Date: Sat, 26 Mar 2011 10:38:54 -0700 From: Freddie Cash <fjwcash@gmail.com> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: freebsd-fs@freebsd.org Subject: Re: tying down adaX to physical interfaces Message-ID: <AANLkTim5rTmhXeLFaTC21BZS58_EteNM7Px-UeeiVsGX@mail.gmail.com> In-Reply-To: <20110326100941.GA50429@icarus.home.lan> References: <AFDA19F9-DC78-463D-862D-6E4F3CB2C2C3@deman.com> <20110326003818.GT78089@deviant.kiev.zoral.com.ua> <D665B3EE-34D6-4125-A9C1-06C71548F7F5@deman.com> <20110326051643.GA43364@icarus.home.lan> <20110326095444.GV78089@deviant.kiev.zoral.com.ua> <20110326100941.GA50429@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Mar 26, 2011 at 3:09 AM, Jeremy Chadwick <freebsd@jdc.parodius.com> wrote: > On Sat, Mar 26, 2011 at 11:54:44AM +0200, Kostik Belousov wrote: >> On Fri, Mar 25, 2011 at 10:16:43PM -0700, Jeremy Chadwick wrote: >> > Why would the disk number change on a drive swap? =C2=A0This doesn't h= appen >> > on my Intel ICH9R controller on *any* Supermicro X7xxx or Supermicro >> > PDxxx board I have access to. >> Because the order of enumeration of controllers depends on the >> BIOS, and is not consistent among boots. Also, it changes if you >> swap controllers or insert disks into the free bays in the backplane. > > Re: insert disks into free bays: it behaves as I described in my post > (paragraph #7): > > http://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011039.html > > If someone wants me to prove it, I'll be more than happy to start > removing/inserting disks on my system here at home to show exactly what > happens (using ICH9xx with ahci.ko). =C2=A0I would prove it as well with = our > production machines but I'd have to physically be in the co-lo to swap > the disk. =C2=A0:-) > > The OP only mentioned that he was concerned with device names changing > if he swapped disks. =C2=A0I have not seen hot-swapping (specifically > removal of old disk, insertion of new disk) result in the device number > increasing -- ever. Reread the original post. :) The point of the post is "how do you keep device bus enumeration the same across reboots". Reboot is mentioned a couple of times in the post. :) The OP wants to know how to populate X out of Y ports on a controller, and have the numbering remain the same across reboots, when adding/removing drives. Without using hint.* entries in /boot/loader.conf, you can't. AFAIK, there's not CAM-based equivalent to ATA_STATIC_NUMBERING in the kernel (or whatever that option is called). Thus, you have to resort to labelling the drives/partitions in one fashion or another, so that no matter what the underlying device node is, the "name" of the drive never changes. --=20 Freddie Cash fjwcash@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTim5rTmhXeLFaTC21BZS58_EteNM7Px-UeeiVsGX>