🚀 go-pugleaf

In article <slrng5r5kl.5uv.felixk@carrot.cabbage.patch>,
Felix Karpfen  <felix@spodzone.org.uk> wrote:
>I had a major crash. And my file system was corrupted very badly.
>It is still unclear why it happened; but all is fixed now (apart
>from the files in "lost+found") and I refrain from spelling out the
>details.  However, I would have been history, if I had not had a backup
>fully-operational (Linux) system on my box from which to repair the
>corrupted disk partition.

Perhaps, but a lot can be achieved with a boot CD.

>Thank you for the advice and the pointer to the "file" command. The
>output of the "file" command reads:
>
>[felixk@ ~]$ file 75584621
>75584621: ERROR: cannot open `75584621' (No such file or directory)
>
>- which is probably just another indication that I was in big trouble!

Were you in the appropriate lost+found directory when you
issued that command.  The argument to "file" is a filename
and 75584621 was one of the lost+found files you listed
in your OP.  Unless the file system has been further corrupted
"file" should be able to deal with it.

So, on my system:
  # file /var/run/cups/cups.sock
  /var/run/cups/cups.sock: socket
  # file /etc/passwd
  /etc/passwd: ASCII text
  # file /
  /: directory

and, in your case, you would want:
  # file /lost+found/xxx

(where xxx is the name of some file in the lost+found directory)

>I assume thaat I can safely delete the entries in "lost+found" since 
>everything works again and none of the entries appear to be missed.

Yes.  All that stuff above is just a suggestion for when you
don't know what a file is.  As all the files in lost+found
were "s" files, all it'll tell you is that they were sockets.
Nevertheless, it should have worked.

Have fun,

Robert.
-- 
Robert Swan		| No, not the antarctic adventurer.
swan.r.l@gmail.com	| No, not the Canberra porn monger.
			| Yes, that's right, the boring one.