I just added a 60GB drive bringing my capacity to 100Gigs and I decided to wipe my empeg clean and setup mp3tofid to keep my stuff in check. Everything was going good until I hit about 44% of my 80Gig upload with this error:

[snip]
drive1/fids/_0000f/
write failed on drive0/fids/_00033/b80 : Success
rsync error: error in file IO (code 11) at receiver.c(244)
rsync: connection unexpectedly closed (393191 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(150)
+ rom+ swapoff /swapfile
empeg:/#

So /drive0 is my older 40GB drive, does this mean that there's a problem with that drive?

Thanks,
Ajay

Not sure how mp3tofid and rsync handles it - but might it be that drive0 is simply full? (ie rsync doesn't realise that it should split the contents across two drives)
I'd Ctrl-C out to the shell and take a look...

/Michael

You have to use an option on mp3tofid to tell it to balance the fids across non size matched discs. I've got a 30gb and 20gb and use the following command :-

mp3tofid -Iis2 33 /data/mp3 /data/empeg/christa

The 33 is the part of the split. Although it looks wrong, my player is pretty balanced.

-2: percentage of files on second drive
-s: spread playlists over both drives

thanks, that was it. I have a 40GB and a 60GB drive so I needed to use the "-2 60" parameter to mp3tofid. That tells it to put 60% of the mp3's on the second drive.

What's the easiest way to check the disk sizes on the empeg? I had to manually create a /etc/mtab file just so I could run 'df'. Is there a better way?

later,
ajay

df .

That's 'df', followed by a dot. This tells df to ignore /etc/mtab and just check the space on the current drive. So you can use the following as well:

df /drive0
df /drive1