Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!news.kei.com!sol.ctr.columbia.edu!howland.reston.ans.net!cs.utexas.edu!convex!seas.smu.edu!utacfd.uta.edu!rwsys!hammy!gordon From: gordon@sneaky.lonestar.org (Gordon Burditt) Subject: Re: [FreeBSD] free diskspace? References: <gate.8oaTFc1w165w@subway.hacktic.nl> <2gmsqn$qo9@pdq.coe.montana.edu> <CJF8H5.E8p@cogsci.ed.ac.uk> <2gvhmt$bv5@pdq.coe.montana.edu> Organization: /usr/lib/news/organi[sz]ation Date: Fri, 14 Jan 1994 23:26:25 GMT Message-ID: <CJn7sG.9y0@sneaky.lonestar.org> Lines: 20 >I believe the poster was Chris Torek, and although changing it from 10% to >5% might be a good idea, I've no idea on where the changes need to go in >the FS code to make 5% the default. You can change the free space overhead of an existing file system with tunefs(8). See the -m option. If you really want to change the default value, it is used as the -m option in newfs(8) and tunefs(8). In newfs.c, change the define of MINFREE. In tunefs(8), the default doesn't seem to be used, but 10 is used as the dividing line for optimization of space vs. time in handling the -m option (look for "case 'm':). (No, I have not tested that this is the only place where the default is used.) I don't see any particular reason why the default value of minfree should be needed in the kernel. It uses the current value read from the file system. Gordon L. Burditt sneaky.lonestar.org!gordon