Date: Thu, 09 Jul 2009 14:32:59 -0700 From: Marcel Moolenaar <xcllnt@mac.com> To: Pawel Jakub Dawidek <pjd@FreeBSD.org> Cc: Ivan Voras <ivoras@freebsd.org>, freebsd-geom@freebsd.org Subject: Re: glabel and real disk IDs Message-ID: <C3B56501-1F02-42FC-B848-DD3969965E82@mac.com> In-Reply-To: <20090709200102.GA2438@garage.freebsd.pl> References: <h34lml$6fv$1@ger.gmane.org> <20090709200102.GA2438@garage.freebsd.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 9, 2009, at 1:01 PM, Pawel Jakub Dawidek wrote: > >> The purpose of this would be to have a unique disk ID without >> explicitly >> setting a label (e.g. as is commonly advised for ZFS and drive >> swapping). > > I guess you advice that? There is no such need when it comes to ZFS. > ZFS > can find his components just fine without using their names. Disk IDs > were added for ZFS in the past, but now they serve no purpose, I'd > prefer to remove them altogether or just leave them for informational > purpose as they exist now. Just as an FYI: I see ZFS getting confused when disks are shuffled around. The confusion is the result of having device paths stored in the ZFS label match the device name of some other vdev that part of the same pool. Replacing a device with itself doesn't help, because ZFS complains that the vdev is part of an active pool in that case. It seems that only labels will work here... -- Marcel Moolenaar xcllnt@mac.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C3B56501-1F02-42FC-B848-DD3969965E82>