I know that some people are running to 2X 60GB drives.

But as drives are sure to get bigger is there a limit the controller in the rio supports?

Thanks

There is no controller, the drives just hook to the bus with a couple of buffers. The limit is only in the linux kernel, and as that can be upgraded then there shouldn't be any issues.

The only real limitation is available memory to store the packed database in ram so that the drives can spin down during playback. That and enough ram/swap space to be able to run fsck.

Hugo

Ah, I 'm quite curious about that as well.

Woud that mean that with 120Gb we've about reached the limit to store that database in the RAM, or is there still a LOT of headroom left?
Wouldn't it be also true that MK2a's have a bit more headroom than MK2's or MK1's, since they have a lot more RAM onboard? (comparing to the MK1 anyway)

Well I have no idea about the RAM requirements for synching and fscking but I do know that 48 bit LBA support is already incorporated into the linux kernel. It would just need porting to the current empeg kernel and you'd be right for years and years.

The size of the database depends on the number of tunes. You can work out the size by looking at the size of the files in /drive0/var - ie, database, playlists, tags. Some people may fill 120GB by using 320kbit and have a smaller database than a 60GB user with 128kbit tunes.

MK2as have a lot more headroom with their extra 4MB. Mk1s are severely strapped for space as is, only having 8MB.

There is no hard limit, the database just takes ram from the playback cache - bigger database, less playback cache. When the playback cache gets too small, things can get upset.

Hugo

okay maybe i have the wong end of the electronic stick here.

If i have all my tunes listed in two trees of playlists like genre and A to Z does this double the size of my database

I may be wrong, but I dont think your setup would make a difference... isn't the database comprised of small files that accompany each mp3? And the accompanying file (sp?) lists the tag info and what playlists the mp3 appears in?

If i have all my tunes listed in two trees of playlists like genre and A to Z does this double the size of my database

No. It will double the size of your playlist database, but unless your files all appear in hundreds of playlists, that'll be much smaller than the tag database that Hugo's mainly talking about.

Peter

okay that is clear