Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!cornell!rochester!pt.cs.cmu.edu!drycas.club.cc.cmu.edu!zardoz.club.cc.cmu.edu!ddj
From: ddj@zardoz.club.cc.cmu.edu (Doug DeJulio)
Newsgroups: comp.sys.next
Subject: Re: disk space problem
Keywords: fsck df disk space
Message-ID: <1991Jun21.142638.5173@zardoz.club.cc.cmu.edu>
Date: 21 Jun 91 14:26:38 GMT
References: <1991Jun20.211954.3066@milton.u.washington.edu>
Organization: The Castle Anthrax
Lines: 27

In article <1991Jun20.211954.3066@milton.u.washington.edu> dwatola@nextasy2 (David Watola) writes:
>until now.  this morning, the disk was completely full.  i closed all of
>my open files and quit all my editing sessions.  however, without logging
>out, i called up the mini-monitor and typed 'reboot'--the 'help' command
>says this does a sync and reboot rather than just a reboot, so it should be
>a clean reboot, right?  in any case, this is often how i do it anyway.  and
>had no trouble until now.
>
>after the reboot, i logged in to find that my dock was gone...

Yes, I remember this problem occuring on my machine before I got a
huge external disk.  Basically, if memory serves, if you end a session
(log out, reboot) while the disk is full, your workspace goes kabloey.
If you can bring it below 100% before you log out or reboot, things
work okay.  I did things like su-ing to root and moving large files to
floppies to take care of this.  Of course, now I have one of the
mid-sized (~650 meg formatted) Fujitsu disks, and the problem is gone...

>worse than that, i only had 1.6M of disk space free.  if you thought 3.6M was
>bad, this is crippling.  the swap file was its proper size; i could find no
>other files to account for this space.  

Look in the /lost+found directory, there might be some files there.
You might even find some of the data you lost.
-- 
Doug DeJulio
ddj@zardoz.club.cc.cmu.edu