Date: Fri, 25 Jan 2013 12:58:15 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Jeremy Chadwick <jdc@koitsu.org> Cc: freebsd@deman.com, freebsd-stable@freebsd.org Subject: Re: RFC: Suggesting ZFS "best practices" in FreeBSD Message-ID: <alpine.BSF.2.00.1301251249500.5564@wonkity.com> In-Reply-To: <20130124174039.GA35811@icarus.home.lan> References: <20130124174039.GA35811@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 24 Jan 2013, Jeremy Chadwick wrote: >>> #1. Map the physical drive slots to how they show up in FBSD so if a >>> disk is removed and the machine is rebooted all the disks after that >>> removed one do not have an 'off by one error'. i.e. if you have >>> ada0-ada14 and remove ada8 then reboot - normally FBSD skips that >>> missing ada8 drive and the next drive (that used to be ada9) is now >>> called ada8 and so on... >> >> How do you do that? If I'm in that situation, I think I could find the >> bad drive, or at least the good ones, with diskinfo and the drive serial >> number. One suggestion I saw somewhere was to use disk serial numbers >> for label values. > > The term FreeBSD uses for this is called "wiring down" or "wired down", > and is documented in CAM(4). It's come up repeatedly over the years but > for whatever reason people overlook it or can't find it. I was aware of it, it just seems like there ought to be a better way to identify drives than by messing with the hardware configuration. Something more elegant, less tied to changing the hardware configuration of the host. Assigning the drive serial number as a label, for example.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1301251249500.5564>