ZFS pool restructuring and emergency repair

Matthew Seaman m.seaman at infracaninophile.co.uk
Mon Jun 22 21:46:47 UTC 2015


On 22/06/2015 22:19, Quartz wrote:
>>> So I take it that, aside from messing with a gvirstor/ sparse disk
>>> image, there's still no way to really handle this because there's still
>>> no way to shrink a pool after creation?
>>
>> Correct. There's no way to shrink a pool ever.
> 
> Drat, that's what I thought. Oh well.

Although in one of Matt Ahrens talks at BSDCan he spoke of plans to
change this.  Essentially you'ld be able to offline a vdev, and a
background process (like scrub) would copy all the data blocks from that
device to elsewhere in the pool.  Once finished, the devices making up
the vdev could be physically removed.

	Cheers,

	Matthew



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 971 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20150622/b21e58dd/attachment.sig>


More information about the freebsd-fs mailing list