kovar%husc4@talcott.harvard.edu (12/15/88)
I've been using my Sun386i as a file server for my Mac using a Cayman GatorBox. Somewhere along the line, it created some files that the system did not like. Through some mechanism that I've since forgotten, I managed to get rid of them. Unfortunately, they reappeared when I used fsck. Here is the system's respose to my inquiries about the files and my attempts to remove them: Script started on Sat Dec 3 16:24:05 1988 {daedalus:SUPERUSER:4} ls lost+found #006191/ #089126/ {daedalus:SUPERUSER:5} ls lost+found/#006191 lost+found/#006191/arpa/nameser.h not found lost+found/#006191/%arpa/nameser.h not found {daedalus:SUPERUSER:6} ls lost+found/#089126 lost+found/#089126/arpa/nameser.h not found lost+found/#089126/%arpa/nameser.h not found lost+found/#089126/net/if.h not found lost+found/#089126/%net/if.h not found lost+found/#089126/netinet/in.h not found lost+found/#089126/%netinet/in.h not found {daedalus:SUPERUSER:7} rm -rf lost+found/* rm: internal synchronization error: lost+found/#006191, nameser.h, arpa/nameser.h rm: internal synchronization error: lost+found/#006191, nameser.h, %arpa/nameser.h rm: internal synchronization error: lost+found/#089126, nameser.h, arpa/nameser.h rm: internal synchronization error: lost+found/#089126, nameser.h, %arpa/nameser.h rm: internal synchronization error: lost+found/#089126, if.h, net/if.h rm: internal synchronization error: lost+found/#089126, if.h, %net/if.h rm: internal synchronization error: lost+found/#089126, in.h, netinet/in.h rm: internal synchronization error: lost+found/#089126, in.h, %netinet/in.h rm: internal synchronization error: lost+found/#089126, errno.h, sys/errno.h {daedalus:SUPERUSER:8} unlink lost+found/#006191 {daedalus:SUPERUSER:9} ls lost+found #006191/ #089126/ Any suggestions on how to remove these files would be appreciated. -David Kovar Technical Consultant Harvard University [[ That could be tricky. Those files look like directories that got unlinked. I suspect that they still exist as directories, but the files that used to be contained in the directories are gone. You could try clearing the two inodes for these files (6191 and 89126) with "clri" and then run another fsck (both with the partition unmounted if possible). You might get more lost files, so just iterate this process until everything gets straightened out. You should probably do this in single user mode, I would think. No guarantees on this advice---use at your own risk. --wnl ]]
corwin@talcott.harvard.edu (-David C. Kovar) (12/16/88)
I sent an article in describing a problem I'd run into on a Sun386i with some files I could not get rid of. I've since discovered something that changes the problem drastically and would like to, if possible, cancel the previous article. I'll resubmit it later. Thanks. [[ Well, I didn't catch it in time. So I'm sending this out to let all the readers know. --wnl ]] -David Kovar