Date: Sun, 14 Aug 2005 21:34:32 -0700 From: Lei Sun <lei.sun@gmail.com> To: Glenn Dawson <glenn@antimatter.net> Cc: questions@freebsd.org, cpghost <cpghost@cordula.ws> Subject: Re: disk fragmentation, <0%? Message-ID: <d396fddf05081421343aeded9d@mail.gmail.com> In-Reply-To: <6.1.0.6.2.20050814131957.10dd4160@cobalt.antimatter.net> References: <d396fddf050813235443c72213@mail.gmail.com> <6.1.0.6.2.20050814000146.0535bb50@cobalt.antimatter.net> <20050814191842.GA1358@bsdbox.farid-hajji.net> <6.1.0.6.2.20050814131957.10dd4160@cobalt.antimatter.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the good answers. But can anyone tell me why the capacity is going negative? and not full? > Filesystem Size Used Avail Capacity Mounted on > /dev/ar0s1e 248M -278K 228M -0% /tmp Thanks a lot Lei On 8/14/05, Glenn Dawson <glenn@antimatter.net> wrote: > At 12:18 PM 8/14/2005, cpghost wrote: > >On Sun, Aug 14, 2005 at 12:09:19AM -0700, Glenn Dawson wrote: > > > >2. How come /tmp is -0% in size? -278K? What had happened? as I have > > > >never experienced this in the previous installs on the exact same > > > >hardware. > > > > > > Not sure about that one. Maybe someone else has an answer. > > > >This is a FAQ. > > > >The available space is always computed after subtracting some space > >that would be only available to root (typically around 5% or 10% > >of the partition size). >=20 > The default is 8%. >=20 > > This free space is necessary to avoid internal > >fragmentation and to keep the file system going. Root may be able > >to "borrow" some space from this (in which case the capacity goes > >below 0%), but it is not advisable to keep the file system so full, > >so it should be only for a limited period of time. >=20 > The reason for having the reserved space is to allow the functions that > allocate space to be able to find contiguous free space. When the disk i= s > nearly full it takes longer and longer to locate contiguous space, which > can lead to performance problems. >=20 >=20 > >In your example, you're 278K over the limit; and should delete some > >files to make space ASAP. Should /tmp fill up more, it will soon become > >inoperable. >=20 > From the original message: >=20 > Filesystem Size Used Avail Capacity Mounted on > /dev/ar0s1e 248M -278K 228M -0% /tmp >=20 > This shows that /tmp is empty. If the reserved space was being encroache= d > upon, it would show > 100% capacity, and available bytes would go negativ= e, > not bytes used. >=20 > It would look something like this: >=20 > Filesystem Size Used Avail Capacity Mounted on > /dev/ad0s1a 248M 238M -10M 105% / >=20 > I've never seen the capacity go negative before, which is why I suggested > someone else might know the answer. >=20 > -Glenn >=20 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d396fddf05081421343aeded9d>