Bug#466075: more information about corrupted database

[Alexander Dahl]

In the case mpd fails to start (this is not always the case) the database is always corrupted in a similar way. There is a single keyword in which one character is shifted 16 characters forward. I can open the database (tag_cache) in a text editor, correct this single wrong character and successfully start mpd then. I give some examples of wrong database keywords:

Corrupted       Must be
---------       -------
Gunre           Genre
Qlbum           Album
Dqte            Date



e->u is      65h->75h     is      01100101b->01110101b

I had several other corrupted keywords all with this one wrong character shifted forward. This seems to be one Bit flipped. I double checked RAM with Memtest86+ -- no error. No other application has problems on this machine. I guessed the error appeared always at the same line or even same byte position in the database, but that's not the case. However it's in the same "region" somewhere in the middle of the database between lines 200000 and 300000 and always in the keywords not in the values. I forgot to mention, this is with Debian Lenny and package version 0.13.1-3 and the same machine as with my initial report. It occurs not as often as with the previous version but I guess still every fourth or fifth time I boot the machine.

signature.asc
Description: OpenPGP digital signature