Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!husc6!linus!raybed2!applicon!bambi!webb!webb
From: webb@webb.UUCP
Newsgroups: comp.bugs.misc
Subject: HELP!: Filesystem Full
Message-ID: <30700003@webb>
Date: Tue, 24-Mar-87 15:14:00 EST
Article-I.D.: webb.30700003
Posted: Tue Mar 24 15:14:00 1987
Date-Received: Sat, 28-Mar-87 03:41:38 EST
Lines: 24
Nf-ID: #N:webb:30700003:000:1354
Nf-From: webb.applicon.UUCP!webb    Mar 24 15:14:00 1987


I am having trouble with a VAX 11/730 running 4.2BSD UNIX.  A couple of days 
ago I was running a process in the background that directed its (very verbose)
output into a file in the /usr partition.  Well, after a bit, the message
`/usr:file system is full' began to appear on the console.  Unthinkingly, I
unlinked the file (with rm -f), expecting the process to die as it lost its
standard output pointer, and the disk space to be freed in the process. 
This is not what happened.  I had to kill the process myself, and my /usr
partition is still 96-100% full.  I will not describe the problems this causes.
I have tried using fsck, both with the -p option and without it, to get rid
of this disk space, but to no avail.  I am not even sure that the problem lies
with the file I unlinked while it was still being written into, but that is
my best guess, since /usr was about 34% full before I ran this process, and I am
the only one who uses this machine.  Does anyone have any suggestions on how
I can identify the source of the problem and fix it?  I have tried searching
/usr for large files, and the only ones I found definitely belonged there.
Thanks in advance.

                                Peter Webb.
				 
{allegra|decvax|mit_eddie|utzoo}!linus!raybed2!applicon!webb
or {amd|bbncca|cbosgd|wjh12|ihnp4|yale}!ima!applicon!webb