Date: Sun, 28 Jun 2015 22:04:30 -0400 From: Quartz <quartz@sneakertech.com> To: Warren Block <wblock@wonkity.com>, Chris Stankevitz <chrisstankevitz@gmail.com> Cc: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: Corrupt GPT on ZFS full-disks that shouldn't be using GPT Message-ID: <5590A7AE.9040303@sneakertech.com> In-Reply-To: <alpine.BSF.2.20.1506281526030.60581@wonkity.com> References: <CAPi0psvpvO4Kpbietpzyx1TjyB20hWV%2BCK-y3bWG4OARE1VMSg@mail.gmail.com> <alpine.BSF.2.20.1506280019400.14091@wonkity.com> <CAPi0psv7io6dhqbNxm6gp%2BW1npmNoU1agF%2Bt=7aEteNmpzqJXQ@mail.gmail.com> <alpine.BSF.2.20.1506281526030.60581@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Remember, ZFS > leaves space unused at the end of a disk to allow for variations in > nominal disk size. Holy what the heck, no it doesn't! One big issue with zfs is that you CANNOT shrink a pool's size once it's been created, for any reason. You can't remove vdevs, and any replacement disk must bigger or exactly equal in size; even a disk with one less sector and you're SOL. This is my biggest gripe with zfs by far and in fact I just asked freebsd-fs about this less than a week ago wondering if it had been addressed finally (it hasn't).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5590A7AE.9040303>