Yes, the command
for i in $(fuser -m /tmp); do ps | grep "^ *$i"; done
will list processes using the /tmp filesystem, while the command
for i in $(fuser -m /tmp); do ls -l /proc/$i/fd | grep deleted; done
will find the probable culprit one, clever, if that is the reason.
-You can stop the processes, reclaiming the space used by them, by using 'rc<service> stop', ex 'rcsmb stop' for samba, 'rcminidlna stop', ... and watching the 'df -h /tmp' command after each one to see when space is again available. Please tell us which one was.
You can use 'rcall status 2>&1 | grep running' to list all running services and names, but don't stop 'inetd', or your connection to the box will probably go down; if that happens, wait three minutes before trying to reconnect.
-I noticed something strange in your 'df -h' command output, device /dev/md2 is mounted under /mnt/Alt-F. That is not usual, have you give /dev/md2 a label under Disk->Filesystems?
That will mount by label under /mnt/Alt-F, and a folder named Alt-F should appear under it. That's OK, but I have not tested that case.
What is the output of 'aufs.sh -l' in your box? It should contain "/mnt/Alt-F/Alt-F=rw", if not than that is an error that needs to be fixed. (please post the full output of 'aufs.sh -l')
-The system log is kept in memory, is small, just 32KB, and circular (so old events are lost). You can use the command 'logread' to display it.
-If settings were lost or can't be saved, its flash filesystem might be corrupt, you might have to clear or format it (System->Settings ) and save settings afterwards before a reboot