Return to BSD News archive
Xref: sserve comp.unix.internals:8135 comp.unix.bsd:15912 Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!gatech!bloom-beacon.mit.edu!pad-thai.cam.ov.com!pad-thai.cam.ov.com!marc From: marc@cam.ov.com (Marc Horowitz) Newsgroups: comp.unix.internals,comp.unix.bsd Subject: Re: Fast File System: optimizing arguments to newfs Date: 16 Jan 1995 18:32:16 GMT Organization: OpenVision Technologies, Inc. Lines: 14 Message-ID: <MARC.95Jan16133216@dun-dun-noodles.cam.ov.com> References: <MARC.95Jan13161859@dun-dun-noodles.cam.ov.com> <3f6udo$dhu@bosnia.pop.psu.edu> NNTP-Posting-Host: dun-dun-noodles.cam.ov.com In-reply-to: barr@pop.psu.edu's message of 13 Jan 1995 17:21:44 -0500 >> >*How* do I want to choose parameters for newfs for these disks? >> >> read newfs(8) and choose logical values, though the only flags >> really useful to fiddle with are the ones mentioned above. (things >> like rotdelay and others aren't an issue with today's faster drives) Well, that's obvious. I have a good idea how to choose -b, -f, and -i. I have no idea how to choose a "logical" value for -m. I know that the free space threshold is there so that the filesystem can allocate blocks efficiently, but I don't know enough about the algorithms involved to know when I'm wasting space, or cutting back too far. Marc