What's you highest inode number? You can find out using

find /your/mp3/dir -printf "%i %p\n" | sort -n"

mp3tofid calculates the fid number from the inode number (inode number + 18) of the source tune. This way, the fid number stays the same, even if you rename or move your source tunes.

I store my mp3 files in a dedicated reiserfs filesystem. I don't know about ext2, but reiserfs allocates inode numbers from one up. If your filesystem does not, your inode numbers might not be consecutive. If you share the filesystem with other stuff, there will be lots of unused fid numbers between your lowest and your highest fid number.

The player database contains one byte for each nonexisting fid number up to the highest number. So high inode numbers result in a large player database.

This makes it impossibe for now to port mp3tofid to cygwin, as its inode numbers in cygwin appear as random 32 bit unsigned integers. This would result in a player database larger than the maximum filesize for most filesystems (2GB).

But your inode numbers might be too high too.

To fix this, I will probably have to create a separate database that tracks inode numbers to fid numbers intelligently. I'm looking into gdbm whether this does what I want.

Pim