On Wed, 6 Dec 2000, David Gewirtz wrote:
Well, I can't be sure what caused it, but the end result was that Linux'
crash had some serious filesystem errors. I did an fsck and the filesystem
now seems better, but there are a heck of a lot of lost+found nodes.
So, here are my questions (could be Linux-newbie questions, sorry):
* Is there a way to tell what files got chomped by the fsck and have
lost+found nodes?
* Is there a way to check a log for htdig?
* Is an fsck -f -y good enough, or should I reformat and reinstall the hard
drive?
If the machine goes down while there is a lot going on in the file system,
file changes that are in the memory cache don't get written to disk and
that is what fsck cleans up.
Generally, those lost+found nodes are going to be those files that were
being written to at the time of the crash. In most cases, this will be
working files or something along those lines. If you're running and RPM
based distro, I'd run rpm -Va and see if you're missing any files (check
the man page for rpm, this command will also list alterations you have
made to some files).
Last thing is to examine those files in lost+found. Use less against them,
then file if that doesn't make any sense.
Finally, reformatting and reinstalling is a bad habit, break it if you
can. You'll learn much more by trying to fix things rather than reinstall.
Contary to Windows, with Linux you CAN fix these types of things. :)
Good Luck,
Bill Carlson
--
Systems Programmer[EMAIL PROTECTED]| Opinions are mine,
Virtual Hospital http://www.vh.org/| not my employer's.
University of Iowa Hospitals and Clinics|
To unsubscribe from the htdig mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
List archives: http://www.htdig.org/mail/menu.html
FAQ:http://www.htdig.org/FAQ.html
