Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!usenet.ins.cwru.edu!eff!news.kei.com!world!ksr!jfw From: jfw@ksr.com (John F. Woods) Newsgroups: comp.os.386bsd.questions Subject: Re: [NetBSD 0.9] filesystem weirdness? Message-ID: <36146@ksr.com> Date: 1 Dec 93 13:23:44 EST References: <Added.EgzA4=200UdbQeJE5j@andrew.cmu.edu> Sender: news@ksr.com Lines: 21 Todd.Williamson@IUS4.IUS.CS.CMU.EDU writes: >I'm not sure whether I did something wrong, or if this is a "feature," >but I want it fixed: >% df -k >Filesystem kbytes used avail capacity Mounted on >/dev/sd0a 7587 6677 151 98% / >kernfs 1 1 0 100% /kern >/dev/sd0e 191863 183348 -10672 106% /usr >Upon cursory examination, it seems like 10% of my filesystems is >"reserved," and I have to be root in order to write in the last 10%. >So, how to I fix this? Buy a bigger disk drive :-). The answer is that the Berkeley Fast Filesystem normally reserves some disk space so that it can ensure optimal placement of newly created blocks; by default that fraction is 10%. If you insist upon being on the ragged edge of disk space, you can back up your current /usr, do a newfs with 0% reserved (check the newfs manual page for the right options, I don't have it handy), and restore.