Unoffical empeg BBS

Quick Links: Empeg FAQ | RioCar.Org | Hijack | BigDisk Builder | jEmplode | emphatic
Repairs: Repairs

Topic Options
#7221 - 07/09/1999 10:58 database corrupt?
raphael
stranger

Registered: 09/06/1999
Posts: 33
Loc: Austria
My empeg database seems to be corrupt.
I reinstalled the beta6 developer image, but emplode hangs either at
"Checking file integrity" or at "Rebuilding music database".
Although I haven't touched /drive0/fids/* and /drive0/var/database directly,
can I remove those files and empeg will be usable again?

Now that my /drive0/var is empty, I'll try to remove my fids too,
so that I can upload mp3s again.

UPDATE: I found out that
$ :> /drive0/var/tags
$ :> /drive0/var/database
$ cd /drive0/fids ; rm *

lets me remove the mp3s and seemed to be the only way to "repair" the database.
A database recovery function or failover (database.old) would be fine.
IMHO Windoze (NASDAQ: DEVIL:) isn't stable enough to ensure that the system
won't hang while a database write.

--
Raphael Wegmann
raphael@psi.co.at
_________________________
--
Raphael Wegmann
raphael@psi.co.at

Top
#7222 - 08/09/1999 07:26 Re: database corrupt? [Re: raphael]
altman
carpal tunnel

Registered: 19/05/1999
Posts: 3457
Loc: Palo Alto, CA
The database is built from the *1 files in the fids directory: it shouldn't be possible to have it crash there unless there's underlying filesystem corruption. If you ever see this again, it'd be useful to tar up the *1 files and send them to us so we can try and replicate the problem here.

Saying that, we've only ever seen it on an old software release (pre-shipping) which wasn't running fsck when it should have been - in combination with power fail interrupting a download.

Hugo



Top
#7223 - 09/09/1999 18:10 Re: database corrupt? [Re: altman]
jason
stranger

Registered: 31/08/1999
Posts: 28
I think I corrupted my database, too. And, only the second day that I have it... :)

I'm guessing it might have something to do with high ascii characters in the
filename / song name of the mp3's I'm uploading, since that is when the
problems started happening. I also got "Couldn't create filename for fid xx"
from memory) errors on bootup and while emplode was "Rebuilding music database".

I'm running a virgin beta6.

I tried a bunch of things, but eventually gave up. Looking at the initial
message in this thread, I went to remove the db files in /drive0, but "database"
was a zero-length file. I rm'ed it, as well as mv'd all the fid's to another
tmp directory. I now am back to "as shipped", and can start resync'ing mp3's.

Two questions:

Is there any way for me to add the old mp3's (the ones I moved out of the
directory) without transferring them over slow USB again?

And, what are the specifications on allowed characters in mp3 filenames and
song titles wrt to the empeg player and emplode software?

Above all, thanks for the coolest toy I've had in years ... well worth the
wait. I get it installed in my Jeep tomorrow PM, and will spend the rest
of my "free time" hacking away at it...


Top
#7224 - 10/09/1999 12:18 Re: database corrupt? [Re: jason]
altman
carpal tunnel

Registered: 19/05/1999
Posts: 3457
Loc: Palo Alto, CA
High ascii should be ok - the 'can't create filename for fid xx' is ok for fids <0x100, this is just a bug in the scanner.

To move files back: first check the *1 files are OK (ie, they're readable and look sensible) then just copy them over and remove the database/tags files - the database will then be rebuilt.

Hugo



Top