Date: Sun, 24 Apr 2011 17:18:40 -0500 (CDT) From: Dan Mack <mack@macktronics.com> To: Pawel Jakub Dawidek <pjd@FreeBSD.org> Cc: svn-src-head@freebsd.org, Alexander Best <arundel@freebsd.org>, Alexander Motin <mav@FreeBSD.org>, src-committers@freebsd.org, svn-src-all@freebsd.org Subject: Re: svn commit: r220983 - head Message-ID: <20110424171704.L2449@coco.macktronics.com> In-Reply-To: <20110424131804.GB1872@garage.freebsd.pl> References: <201104240923.p3O9N8QG025386@svn.freebsd.org> <20110424095736.GA92492@freebsd.org> <20110424051747.S1757@coco.macktronics.com> <20110424131804.GB1872@garage.freebsd.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 24 Apr 2011, Pawel Jakub Dawidek wrote: > On Sun, Apr 24, 2011 at 05:25:00AM -0500, Dan Mack wrote: >> For those of us using a ZFS root pool built out of /dev/gpt/ >> devices, will these automagically pick up the new names? > > Even if you use adX devices in your ZFS pool and they will suddenly > change to adaY, ZFS should detect this properly and no manual > intervention should be needed. Yep, confirmed. My boot zroot RAID10 pool previously built from ad4, ad6, ad8, ad10 worked without a hitch with the new enumeration scheme: borg# gpart status Name Status Components ada0p1 OK ada0 ada0p2 OK ada0 ada0p3 OK ada0 ada1p1 OK ada1 ada1p2 OK ada1 ada1p3 OK ada1 ada2p1 OK ada2 ada2p2 OK ada2 ada2p3 OK ada2 ada3p1 OK ada3 ada3p2 OK ada3 ada3p3 OK ada3 borg# zpool status pool: zroot state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 gpt/disk0 ONLINE 0 0 0 gpt/disk1 ONLINE 0 0 0 mirror-1 ONLINE 0 0 0 gpt/disk2 ONLINE 0 0 0 gpt/disk3 ONLINE 0 0 0
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110424171704.L2449>