I am trying to restore a system on FreePBX 17 from a FreePBX 16 system, the backup is 3.5GB.
When I try to do the restore it fails with this message.
In Tar.php line 189:
mkdir(): No space left on device
The device is running a 480GB drive so overall it should be fine, I am guessing the location it is being upacked to is limited, how can I resolve this issue and get my system restored?
Howdy! Welcome to the forums.
What is the drive space available in /tmp on your v17 e.g. output from df -h ?
(Also, the Backup module needs an update to allow arbitrary temporary directory selection during Restore, instead of forcing to /tmp in the code – thought there was a GitHub issue for this already, but just opened a new one in case: [bug]: Backup module needs arbitrary temporary directory selection for Restore function · Issue #879 · FreePBX/issue-tracker · GitHub).
[quote=“penguinpbx, post:2, topic:107851”]
You are asking me a very good question, while I have built quite a number of FreePBX instances I don’t claim to be an expert on Linux.
I assume that df -h is a Linux command line request that should give the answer? I will get the box out and try it.
I have also done another box with FreePBX 16 and tried a restore on that, the restore did complete and appears to have all the setting except extensions, trunks and in and outbound rules which seems very odd.
Debian 13, and presumably Debian 12, use tmpfs for /tmp, which means that the available space will depend on RAM and swap file sizes. I assume the swap file size is a function of the RAM size, so a VM with a small virtual RAM could have a relatively limited temporary file space.
That probably explains the issue then, its only a small Gigabyte Mini PC with 4GB of ram. Although the system will run fine with that in operation getting the back up done maybe won’t work. If I can restore it on a FreePBX 6 install I could probably trim it down as it has lots of phone profiles and logs that are not really needed.
Are there any hacks to force the swap file size up? Maybe I need some Debian research here.
You should be able to use swapon to add disk/ssd as additional swap space. That can be done and undone on a live system, but you might find that there is a lot of thrashing; or you could not mount /tmp, and use space on the root filesystem, but you would probably need to go single user to safely transition to and from tmpfs.