Yes, that's right I filled up the debian image last night on my ME1. Serves me right for trying to download a 3.5Gb Linux ISO. The fix was quite simple but I had a few spare minutes to tinker a bit and ended up reconfiguring my Samba shares to make it look tidier. The ME1 can be configured to run a debian image that is preloaded with Samba, SSH and an mldonkey client. Take a look here for more information on how to do that.So here goes, a quick look at the fix.With the d3g.ext2 debian image filled, I had to first clear some space to allow me to tinker. The MLDonkey client software is configured to write all of it's temporary files to /var/lib/mldonkey/temp. Since this is inside the debian image you're not only limited by the 4Gb Fat32 file limit, you're going to be short a few megs for the rest of the operating system and apps that the image holds.The HDD I have in the enclosure is mounted as /mnt/hda, so after SSHing to the device I made a work folder.#mkdir /mnt/hda/work
The mldonkey server had died by this point, due to lack of disk space but if you find yourself in need of this fix you'll have to make sure you stop the server
#/etc/init.d/mldonkey-server stop
Next we take a look in the mldonkey temp folder
#cd /var/lib/mldonkey/temp
#ls -l
The complete contents of this folder need to be moved to the work folder on our HDD.
#mv * /mnt/hda/work
Don't worry about the preservation of permissions on the files being moved, the HDD is Fat32 so they all become rwx for all users and owned by root anyway. Then we remove the folder and create a pointer to our HDD, the mldonkey server software will never know the difference
#cd ..
#rmdir temp
#ln -s temp /mnt/hda/work
Lastly restart the mldonkey server and you'll be up and running again.
#/etc/init.d/mldonkey-server restart
Now then, I mentioned that I tidied up my hdd after I did this tinkering. That was a simple case of moving the debian image to a debian folder and all of my other content to a folder named store.
The debian image needs to be moved from the main telnet login rather than the ssh console (as you'd be trying to move the operating system that you're currently running, and that would never work). Telnet onto the device, edit the file /usr/local/etc/auto and comment (with a #) the lines that mount and chroot the d3g.ext2 image. save that and reboot. I then moved the debian image into a folder named debian, altered the auto file to show the new filepaths and rebooted again. Et Voila! back up and running again with my HDD root folder clear of files (Did I mention I was a digital neat freak).
Lastly I mentioned that my media was moved to a folder named store. This was so I could edit the samba config in /etc/samba/smb.conf to change the path of the shared volume to use the store folder. That way you can't get at my debian image or the mldonkey work folder over samba. one less thing to go wrong!
Next setting the time automatically and fixing the samba shares, so I can access them from my mac.