adams@skippy.berkeley.edu (Jeffrey P. Adams) (06/06/90)
Maybe it's because I don't know what I'm doing, but: My 330Mb hard disk is full. But it's not. The cube won't let me write anything to disk, but when I check the disk space via Workspace Manager it says: (roughly) 100% full 330000K available 295000K used I tried deleting everything that wasn't essential, but it kept insisting I was full. Is this a bug, or am I doing something wrong? Like, is there a utility I have to run to reclaim disk space? Help me quick! Jeff Adams adams@ucscl.ucsc.edu
rca@cs.brown.edu (Ronald C.F. Antony) (06/13/90)
to avoid that a completely filled up disk looses it's content, the disk has 110% or so capacity (of course just a pseudo percentage...) and noone except root can write anything as soon as the 100% out of 110% are reached... Ronald ------------------------------------------------------------------------------ "The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man." Bernhard Shaw | rca@cs.brown.edu or antony@browncog.bitnet
louie@sayshell.umd.edu (Louis A. Mamakos) (06/13/90)
In article <42891@brunix.UUCP> rca@cs.brown.edu (Ronald C.F. Antony) writes: >to avoid that a completely filled up disk looses it's content, the >disk has 110% or so capacity (of course just a pseudo percentage...) >and noone except root can write anything as soon as the 100% out of >110% are reached... This is, of course, nonsense. The reason that that the disk fills at 90% (or 95% or whatever) is a performance issue related to the fact that the NeXT is using the Berkeley Fast File System. If you look at the man page for tunefs(8) you'll see: - - - - - - - - - TUNEFS(8) UNIX Programmer's Manual TUNEFS(8) NAME tunefs - tune up an existing file system SYNOPSIS /usr/etc/tunefs tuneup-options special|filesys DESCRIPTION Tunefs is designed to change the dynamic parameters of a file system which affect the layout policies. The parame- ters which are to be changed are indicated by the flags given below: . . . -m minfree This value specifies the percentage of space held back from normal users; the minimum free space threshold. The default value used is 10%. This value can be set to zero, however up to a factor of three in throughput will be lost over the performance obtained at a 10% threshold. Note that if the value is raised above the current usage level, users will be unable to allocate files until enough files have been deleted to get under the higher threshold. . . . - - - - - - - - - If you wanted to suffer lower performance thruput to the file system, you can tweak the minfree parameter to use more of the "available" disk space. You might also look at the man page for fs(5) for more gory details. Note that "root" can allocate every block on the disk, so that you can have a file system which is 110% full. And don't forget and always remember: You can tune a file system, but you can't tune a fish. louie