> On Tue, 09 Oct 2001 16:37:10 GMT
> DR> Hello,
> DR> Recently, my FreeBSD box suffered a power outage. It wasn't really
> DR> doing anything so I wasn't expecting a problem with this. When the
> DR> power came back on, I booted the machine into single user mode and ran
> DR> fsck manually. It found that an inode was disconnected and it asked me
> DR> if I wanted to salvage it. I said yes, and fsck put the resulting file
> DR> into the /usr/lost+found directory. The file name is #0158774. When I
> DR> try and view the file, it is some kind of binary information. Although
> DR> I have not noticed any problems with the system since, it does make me a
> DR> little nervous to know that a file tht may or may not be required may be
> DR> missing on my /usr partition. Is there a way to find out what file that
> DR> this used to be associated with?
> will tell you what type of file it is.
> will pull any ASCII strings in it (if it is anything like C code).
> will show SCCS version control info.
> will show RCS version control info.
> With a bit of luck the output of one or more of these may give
> enough clues assuming you can't just compare what is on the system now
> with the last backup, look for things that have gone missing and compare
> Directable Mirrors - A Better Way To Focus The Sun
I figured it out. The reason I couldn't do anything with it (including
more, cat, and file) is because the filename starts with a #. When I
did file "#0158774" it said that the file was a gzip compressed file. I
copied it to unknown.gz and ran gunzip on it. As it turns out, the file
is a man page for (8)route. I checked it out and found that the real
man page still exists so I dumped the file. I DID view this particular
man page about 10 minutes before the power outage hit, and someone here
mentioned it was probably some temp file that no one cares about.
Reply to dcrudy at aol dot com.
*!*!* DO NOT HIT REPLY *!*!*
ALL EMAIL SENT TO REPLY ADDRESS WILL BE DELETED!