Path: utzoo!mnetor!uunet!steinmetz!vdsvax!barnett From: barnett@vdsvax.steinmetz.ge.com (Bruce G. Barnett) Newsgroups: comp.unix.questions Subject: Re: Compressing unix disks Message-ID: <4062@vdsvax.steinmetz.ge.com> Date: 14 Mar 88 11:22:51 GMT References: <305@marconi.SW.MCC.COM> <29500023@ccvaxa> Reply-To: barnett@vdsvax.steinmetz.ge.com (Bruce G. Barnett) Organization: General Electric CRD, Schenectady, NY Lines: 18 In article <29500023@ccvaxa> aglew@ccvaxa.UUCP writes: [Discussion on the Berkeley fast file system] |Disk thruput maybe, file thruput no. Lots of activity on a nearly full |disk can result in a file spread across several cylinders, because there |wasn't room on a single cylinder when it was created, although there may |be now. | Perhaps the term "fragmentation" is inappropriate. As I recall, whenever a 'mkdir' is issued, the system finds the largest cylinder group it can. Therefore the best access can be achieved by putting a large number of files in a new directory. That is the theory - anyway. Are there any tricks to keep your Berkeley file system up to snuff? I remember some non-unix operating systems suggesting you put the most frequently used files on first. -- Bruce G. Barnett uunet!steinmetz!barnett