Discovering File System Corruption
bret-walker at northwestern.edu
Tue Jan 10 06:26:35 PST 2006
I have a 6.0-RELEASE-p1 box with a GENERIC kerbnel that I'm having some
I recently reconstituted the machine from being a 5.4 box. I didn't
upgrade, I reinstalled.
When I was trying to install tripwire, kept getting this message:
"./bin/i386-unknown-freebsd_r/siggen missing. Build did not complete
*** Error code 1"
I CVSupped a few times, even deleting the tripwire directory completely
and letting CVSup re-add it. I finally fixed the problem by copying the
missing file from another box.
The maintainer of the the port wrote to me:
" The missing files were missing from the distfile extraction, not the port.
The distfile failed to extract properly. That indicates that either tar
failed (unlikely) or that you have some kind of filesystem problem. You
have a problem much more serious than a mere port that failed to build."
I have run fsck in single user mode many times, each time coming back clean.
I ran fsck -f -p, to make sure I wasn't having any problems like this (
How can I determine what is going on? Do I have filesystem corruption,
or is something else going on?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 2821 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20060110/db82b190/smime.bin
More information about the freebsd-questions