Date: Thu, 30 Jun 2011 01:54:22 -0600 From: Kurt Touet <ktouet@gmail.com> To: Artem Belevich <art@freebsd.org> Cc: freebsd-fs@freebsd.org Subject: Re: ZFS v28 array doesn't expand with larger disks in mirror Message-ID: <BANLkTinFVM-Z79k=1qudjtfoPuQFWpJyTw@mail.gmail.com> In-Reply-To: <BANLkTiksDgVx7T_79g6SsKvWH-aTf%2Bi4sA@mail.gmail.com> References: <BANLkTimx1Y=xXXEqGvnpOk5asPuOftJFLw@mail.gmail.com> <BANLkTiksDgVx7T_79g6SsKvWH-aTf%2Bi4sA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for that info Artem. I have now set that property, exported/imported, and rebooted to no avail. Is this something that needed to be set ahead of time? Thanks, -kurt On Thu, Jun 30, 2011 at 1:03 AM, Artem Belevich <art@freebsd.org> wrote: > On Wed, Jun 29, 2011 at 11:29 PM, Kurt Touet <ktouet@gmail.com> wrote: >> I have an admittedly odd zfs v28 array configuration under stable/8 r223= 484: >> >> # zpool status storage >> =A0pool: storage >> =A0state: ONLINE >> =A0scan: resilvered 1.21T in 10h50m with 0 errors on Wed Jun 29 23:21:46= 2011 >> config: >> >> =A0 =A0 =A0 =A0NAME =A0 =A0 =A0 =A0STATE =A0 =A0 READ WRITE CKSUM >> =A0 =A0 =A0 =A0storage =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 =A0 0 >> =A0 =A0 =A0 =A0 =A0raidz1-0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ad14 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ad6 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ad12 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ad4 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 >> =A0 =A0 =A0 =A0 =A0mirror-1 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ad20 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ad18 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 >> >> This was simply due to the need to expand the size of the original >> raidz1 only array and constraints within the box. =A0All drives in the >> box _were_ 1.5TB. =A0I had a drive in the mirror die this week, and I >> had 2 spare 2TB drives on hand. =A0So, I decided to replace both of the >> 1.5TB drives in the array with 2TB drives (and free up a little more >> space on the box). =A0However, after replacing both drives, the array >> did not expand in size. =A0It still acts as if the mirror contains 1.5TB >> drives: >> >> storage =A0 =A0 6.28T =A0 548G >> =A0raidz1 =A0 =A05.07T =A0 399G >> =A0mirror =A0 =A01.21T =A0 150G >> >> Is this normal behaviour? =A0It was my understanding that zfs >> automatically adapted to having additional drive space in vdevs. > > You still have to set 'autoexpand' property on the pool in order for > expansion to happen. Perevious versions would expand the pool on > re-import or on boot. > > --Artem > >> >> -kurt >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTinFVM-Z79k=1qudjtfoPuQFWpJyTw>