DrHu wrote:I don't know what the question was
, cannot mentally simulate your disk setup and the process you are executing..
..You found the space in the usual place (/home .. which will include anything you want to add up to the MAX space you have available..)), but you didn't start by saying you were using virtualbox
--and despite the descriptions given: the exact nature of your setup for hard drives still eludes me
I'm not using virtualbox for Mint Debian. I followed a partitioning guide for install of Mint Debian and my setup is:
remainder allocated /home
My problem was this: in the default install /tmp is created as a 'virtual' file system, google tmpfs. It is limited to a percentage of your total RAM, in my case it was set to around 750MB - ample space for most tasks.
However I had created an encrypted backup using deja-dup under Ubuntu and it was these files that I was trying to recover. They include a couple of virtualbox hdd's for my VB version of Windows XP and other Linux OS's I was playing with. These are quite big files, the XP one is in excess of 20GB.
Because deja-dup writes the files to /tmp before restoring them, it was rapidly running out of space and thus falling over. This is why I had to stop the tmpfs system at boot. My / partition was also not big enough for the 68GB of VBox files, so I had to symlink /tmp to my /home partition. Having recovered my files, I have now restored the /tmp directory to tmpfs.
Deja-dup is not particularly good at error messages. Instead of telling me that /tmp was full, it told me that there was not enough space in my home directory, which of course is not true. So it took me some time to track down the cause and correct the backup recovery.
I hope this is now clear.