Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 23 Aug 2002 13:43:45 -0400
From:      Chris Ptacek <cptacek@sitaranetworks.com>
To:        "'Giorgos Keramidas'" <keramida@ceid.upatras.gr>, Carlos Carnero <zopewiz@yahoo.com>
Cc:        wmoran@potentialtech.com, freebsd-questions@FreeBSD.ORG
Subject:   RE: optimization changed from TIME to SPACE ?!
Message-ID:  <31269226357BD211979E00A0C9866DAB02BB9988@rios.sitaranetworks.com>

next in thread | raw e-mail | index | archive | help
Actually I have been trying to figure out this myself for a while.  I am
having the same issues (squid cache), TIME to SPACE changes with the
partition at 50-70% used.  From what I have been able to find this has to do
with fragmentation in the partition and not the disk actually being full.  I
actually have a partition dedicated to the cache (/cache) so I am pretty
sure the fragmentation is caused by squid.  Currently I have not been able
to figure our what I can do to ease or prevent these TIME to SPACE changes
(reduce fragmentation).  If you figure anything out please let me know as
well.

  - Chris

> -----Original Message-----
> From: Giorgos Keramidas [mailto:keramida@ceid.upatras.gr]
> Sent: Friday, August 23, 2002 10:04 AM
> To: Carlos Carnero
> Cc: wmoran@potentialtech.com; freebsd-questions@FreeBSD.ORG
> Subject: Re: optimization changed from TIME to SPACE ?!
> 
> 
> On 2002-08-23 09:48 +0000, Carlos Carnero wrote:
> > > Your /var filesystem is almost 100% full.
> >
> > I thought so the moment I saw the message, but for
> > several months now I monitor that box using SNMP and
> > that partition is *always* kept very loose space-wise.
> 
> That's funny, because space optimization kicks in only when the free
> space drops below a certain percentage in FreeBSD's filesystem.  The
> default behavior is to allocate blocks & fragments from a filesystem
> in the fastest way possible, without taking a lot of care to avoid
> excess fragmentation of existing blocks.  When the free space drops
> below a certain percentage, the filesystem code tries to avoid
> fragmenting disk blocks too much, and turns on "space optimization"
> instead of the default "time optimization".  This uses slower
> algorithms for selecting the blocks & fragments of a file when it's
> written to, but saves some space.
> 
> > Filesystem  1K-blocks     Used    Avail Capacity  Mntd
> > /dev/ad0s1a    248047    38637   189567    17%    /
> > /dev/ad0s1f  10163179  3081838  6268287    33%    /usr
> > /dev/ad0s1e  26341315  9609257 14624753    40%    /var
> > procfs              4        4        0   100%   /proc
> 
> Are you sure there aren't peaks in the space usage of this filesystem
> that you might miss while using df?
> 
> -- 
> FreeBSD: The Power to Serve <> http://www.FreeBSD.org
> FreeBSD 5.0-CURRENT #0: Wed Aug 21 22:08:19 EEST 2002
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message
> 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?31269226357BD211979E00A0C9866DAB02BB9988>