peterb@pbear.UUCP (03/01/85)
One possiblity is to ls -i the file to get the inode, and then have your guru (or someone else who will take the blame) to clri that inode. Then run fsck to reclaim the logically lost space. This ought to work, but I am not guarenteeing anything. Remember, only do this on an UNMOUNTED file system else havoc can reak and make thy life not worth the disk space used to record it! And make sure that you fsck the file system afterwords else the filesystem gets lost and the data goes to trash and you suddenly have lots of people ready to turn you into lots of tiny pieces. How in hell does . vanish ??? I thought fsck catches these things. Peter Barada ima!pbear!peterb
adm@cbneb.UUCP (03/11/85)
We had a similar problem (on a 3B20S). I found you could still access the files if you use their full pathnames. You could move them to some other directory, then remove and recreate the directory.