Date: Thu, 24 Jan 2013 09:27:14 +0100 From: Borja Marcos <borjam@sarenet.es> To: Ollivier Robert <roberto@keltia.freenix.fr> Cc: freebsd-fs@freebsd.org Subject: Re: RFC: Suggesting ZFS "best practices" in FreeBSD Message-ID: <0AF9A29D-5B5A-4CB6-B880-7F43CA7FC612@sarenet.es> In-Reply-To: <20130123143018.GA5533@roberto02-aw.eurocontrol.fr> References: <314B600D-E8E6-4300-B60F-33D5FA5A39CF@sarenet.es> <alpine.BSF.2.00.1301220759420.61512@wonkity.com> <CAOjFWZ4X8src2DQV%2B49DjKgT7pgMbR69j%2BiRAq-UoVA0Lz3xcg@mail.gmail.com> <20130123143018.GA5533@roberto02-aw.eurocontrol.fr>
index | next in thread | previous in thread | raw e-mail
On Jan 23, 2013, at 3:30 PM, Ollivier Robert wrote: > According to Freddie Cash on Tue, Jan 22, 2013 at 03:02:40PM -0800: >> The ZFS metadata on disk allows you to move disks around in a system and >> still import the pool, correct. > > Even better, a few years ago before I enabled AHCI on my machine, the > drives were named adX. After I started using AHCI, the drives became adaY > and it still booted fine. Yes, that's right. As an example, yesterday I used the gnop kludge to have a SSD recognized as a 4K-sector drive. After a reboot, ZFS was able to locate the device even though the named gnop device had disappeared. However, remember that the Murphy's field is enormously intense around anything that holds data, especially if that data is important. Yes, it works, but it's better not to rely too much on error recovery mechanisms. And there is at least one situation in which the dynamic renumbering causes trouble (failure + reboot) which is not so rare on high uptime machines with many disks. Borja.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0AF9A29D-5B5A-4CB6-B880-7F43CA7FC612>