Date: Tue, 2 Jan 2018 13:52:54 -0600 From: Adam Vande More <amvandemore@gmail.com> To: pete wright <nomadlogic@gmail.com> Cc: freebsd-questions <questions@freebsd.org> Subject: Re: zpool fragmentation Message-ID: <CA%2BtpaK0r=DAOi5pA%2BYHC4u7C12EjRc6sUE1tdQJU-EW5YWFVqw@mail.gmail.com> In-Reply-To: <CAGBmCT6tjinhjQrzs08zVUoK6OzUB1HzovN=cOmAWOfNzrRPsA@mail.gmail.com> References: <CAGBmCT6tjinhjQrzs08zVUoK6OzUB1HzovN=cOmAWOfNzrRPsA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 2, 2018 at 12:40 PM, pete wright <nomadlogic@gmail.com> wrote: > Hi there, > I was wondering how others here on the list deal with zpool > fragmentation. My general purpose laptop uses zroot, and I've noticed > over time fragmentation of my pool has grown to %42: > > $ zpool list > NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT > zroot 230G 87.3G 143G - 42% 37% 1.00x ONLINE - > $ > > I guess I have two questions: > 1) is fragmentation generally bad, or just a fact of life for a system > with lots of churn? > Yes but impact also depends on pool config. > 2) if it is bad, are there any coping mechanisms people use to reduce > fragmentation? > Keep lots of free space. -- Adam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BtpaK0r=DAOi5pA%2BYHC4u7C12EjRc6sUE1tdQJU-EW5YWFVqw>