Date: Thu, 12 Dec 2002 20:30:17 +0100 From: Paul Everlund <tdv94ped@cs.umu.se> To: Jens Rehsack <rehsack@liwing.de> Cc: C J Michaels <cjm2@earthling.net>, questions@FreeBSD.org, bri@sonicboom.org, wmoran@potentialtech.com Subject: Re: ...changed from TIME to SPACE Message-ID: <3DF8E3C9.3030701@cs.umu.se> References: <Pine.GSO.4.44.0212111629180.22586-100000@kvist.cs.umu.se> <1299.216.153.201.47.1039623659.squirrel@www.27in.tv> <3DF76F78.8040100@cs.umu.se> <3DF772FE.7080108@liwing.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Jens Rehsack wrote: > Paul Everlund wrote: > >> C J Michaels wrote: >> >>> Some time in the recent past Paul Everlund scribbled: >>> >>> >Hi list! >>> > >>> >What does this mean? >>> > >>> ># sysctl kern.msgbuf >>> >[snip] >>> ><5>/var: optimization changed from TIME to SPACE >>> ><118>Dec 10 11:36:12 fw /kernel: /var: optimization changed from >>> TIME to >>> >SPACE [snip] >>> >>> It means that your /var filesystem is nearly full. The kernel is now >>> trying to maximize the amout of free full blocks on the filesystem. >>> >>> >From fs(5) manpage: >>> === >>> The element fs_optim specifies whether the file system should try to >>> min- >>> imize the time spent allocating blocks, or if it should attempt to mini- >>> mize the space fragmentation on the disk. If the value of fs_minfree >>> (see above) is less than 10%, then the file system defaults to >>> optimizing >>> for space to avoid running out of full sized blocks. If the value of >>> minfree is greater than or equal to 10%, fragmentation is unlikely to be >>> problematical, and the file system defaults to optimizing for time. >>> === >>> >>> Some other good reads would be tunefs(8), newfs(8), and the mailing list >>> archives. >> >> >> >> Thank you Chris and Jens for your replies! >> >> A full file system on /var triggered it? >> >> # df -k >> Filesystem 1K-blocks Used Avail Capacity Mounted on >> /dev/ad1s1a 65470 40452 19782 67% / >> /dev/ad0s1e 2030062 801262 1066396 43% /usr >> /dev/ad1s1e 35230 17770 14642 55% /var >> procfs 4 4 0 100% /proc >> >> It doesn't look full to me. >> >> Best regards, >> Paul >> > Try 'df -ik' # df -ik Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/ad1s1a 65470 40452 19782 67% 1517 6801 18% / /dev/ad0s1e 2030062 801262 1066396 43% 110510 144464 43% /usr /dev/ad1s1e 35230 17512 14900 54% 825 3653 18% /var procfs 4 4 0 100% 49 483 9% /proc The i-nodes are fine too. Anyway, I guess it is as Bill Moran wrote, that a temporary file was created, that made it change, and somewere in the logs a change back should be found. Will check it later. Thank you all for your replies! In the future, now I know what TIME to SPACE and vice versa means! Best regards, Paul 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?3DF8E3C9.3030701>