Date: Sun, 21 Sep 2014 14:17:34 +0100 From: "Steven Hartland" <killing@multiplay.co.uk> To: "Beeblebrox" <zaphod@berentweb.com>, <freebsd-current@freebsd.org> Subject: Re: zpool frag Message-ID: <5EE253EAE0A84950B3CEA19751580825@multiplay.co.uk> References: <1411289830171-5950788.post@n5.nabble.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Backup the pool and restore it is the only way I'm aware of. ----- Original Message ----- From: "Beeblebrox" <zaphod@berentweb.com> To: <freebsd-current@freebsd.org> Sent: Sunday, September 21, 2014 9:57 AM Subject: zpool frag > FRAG means fragmentation, right? Zpool fragmentation? That's news to me. If > this is real how do I fix it? > > NAME SIZE ALLOC FREE FRAG EXPANDSZ CAP DEDUP HEALTH ALTROOT > pool1 75.5G 53.7G 21.8G 60% - 71% 1.00x ONLINE - > pool2 48.8G 26.2G 22.6G 68% - 53% 1.00x ONLINE - > pool3 204G 177G 27.0G 53% - 86% 1.11x ONLINE - > > Regards. > > > > ----- > FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS > -- > View this message in context: http://freebsd.1045724.n5.nabble.com/zpool-frag-tp5950788.html > Sent from the freebsd-current mailing list archive at Nabble.com. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5EE253EAE0A84950B3CEA19751580825>