|
Home > Archive > alt.os.linux > December 2002 > Corrupted "updatedb" Error Message
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Corrupted "updatedb" Error Message
|
|
|
| After performing "update -u" or "updatedb" on my Red Hat 7.1 box,
I get an error message when trying to locate a file. For example,
when I type:
# locate whereis
I get:
fatal error: locate: decode_db: 'pathlen == -3'! Corrupt Database!
I tried e2fsck, but found no errors and the error message above
returned.
Thanks for your help!
| |
| +Chiron+ 2002-12-09, 5:25 pm |
| -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
MFH tempted the fates in alt.os.linux
by proclaiming the following to be true:
1. Don't cross post your message unless it's necessary.
Failing to RTFM does not make your qustion necessary.
> After performing "update -u" or "updatedb" on my Red Hat 7.1 box,
> I get an error message when trying to locate a file. For example,
> when I type:
RTFM
man updatedb
man locate
> fatal error: locate: decode_db: 'pathlen == -3'! Corrupt Database!
So?
RTFM.
Delete the database & rebuild it.
> I tried e2fsck, but found no errors and the error message above
> returned.
RTFM.
'updatedb' has nothing to do with the underlying filesystem (fsck).
it's a file/directory database, not a filesystem.
> Thanks for your help!
RTFM.
- --
+Chiron+ ( Passion is that funny feeling that drives a
GnuPG Pub Key 848D1A2D -o) ) man to bite a woman's neck because she has
Linux Kernel 2.4.20 /\\ ( beautiful legs.
Slackware 8.1 *w00t* _\_v )
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.1 (GNU/Linux)
iD8DBQE99SJxe8wcrYSNGi0RArA8AK
C4Sfkk0Qh2mm4sy7+60lJfRZxY7gCd
HhRY
HXmfsTAlD1gd42tnAHJH8ok=
=x1hf
-----END PGP SIGNATURE-----
| |
| Paul Lutus 2002-12-09, 6:24 pm |
| On Mon, 09 Dec 2002 18:02:39 +0000, MFH wrote:
> After performing "update -u" or "updatedb" on my Red Hat 7.1 box, I get
> an error message when trying to locate a file. For example, when I type:
>
> # locate whereis
>
> I get:
>
> fatal error: locate: decode_db: 'pathlen == -3'! Corrupt Database!
>
> I tried e2fsck, but found no errors and the error message above
> returned.
>
> Thanks for your help!
Try running "updatedb" again, this time without closing the terminal
window you started it from. 
Or:
# updatedb &
The program "updatedb" calls, /usr/bin/slocate, completely recreates the
database on each run, so the only way to have a corrupt database is to
kill the process or run out of drive space.
--
Paul Lutus
http://www.arachnoid.com
| |
|
| Thank you for your constructive recommendations. It turns out
that there is a more recent version of slocate that, among other
things, fixes a bug when slocate encounters very long path names,
which appears to be the source of the problem I was having.
(The RTFM guy evidently does not RTFM himself, or he would have
realized that the man pages do not address the problem I was
posing. I'm soooo glad I outgrew that arogance 35 years ago...)
Thanks!
Paul Lutus wrote:
> On Mon, 09 Dec 2002 18:02:39 +0000, MFH wrote:
>
>
>>After performing "update -u" or "updatedb" on my Red Hat 7.1 box, I get
>>an error message when trying to locate a file. For example, when I type:
>>
>># locate whereis
>>
>>I get:
>>
>>fatal error: locate: decode_db: 'pathlen == -3'! Corrupt Database!
>>
>>I tried e2fsck, but found no errors and the error message above
>>returned.
>>
>>Thanks for your help!
>
>
> Try running "updatedb" again, this time without closing the terminal
> window you started it from.
>
> Or:
>
> # updatedb &
>
> The program "updatedb" calls, /usr/bin/slocate, completely recreates the
> database on each run, so the only way to have a corrupt database is to
> kill the process or run out of drive space.
>
| |
| +Chiron+ 2002-12-09, 9:24 pm |
| -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
MFH tempted the fates in alt.os.linux
by proclaiming the following to be true:
> (The RTFM guy evidently does not RTFM himself, or he would have
> realized that the man pages do not address the problem I was
> posing. I'm soooo glad I outgrew that arogance 35 years ago...)
If you're so smart, why did you have this issue to begin with skippy?
It's a shame you haven't outgrown your stupidity in those 35 years.
Now then:
What part of "Stop Crosposting" didn't you comprehend?
If you recieved a less-than-satisfactory answer, perhaps you need to
seriously re-evaluate your question - no?
You gave ZERO useful information.
You did not mention what version of locate you used.
You did not mention what distro you were using.
You did not RTFM.
You did not do a Google search before posting your question.
You did not ask anything specific other than "this is what it does: why?"
You have only uorself to blame for your own incompetence.
Read:
How To Ask Questions The Smart Way
http://www.tuxedo.org/~esr/faqs/smart-questions.html
Maybe, just mybe next time you'll have a clue before you post any more
empty "fix this for me" questions.
- --
+Chiron+ ( That is the saddest story I've ever heard. It
GnuPG Pub Key 848D1A2D -o) ) has really touched my heart. And you have my
Linux Kernel 2.4.20 /\\ ( deepest sympathies. Now XXXX off and stop
Slackware 8.1 *w00t* _\_v ) bothering me. -on a T-shirt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.1 (GNU/Linux)
iD8DBQE99Vbye8wcrYSNGi0RArhyAJ
95ljXghGBNl6ENjqmn1la9Jg+eFQCg
lwA8
cRIZLNkNgkQMPYcOlsdFFgA=
=R0sq
-----END PGP SIGNATURE-----
|
|
|
|
|