Revision history [back]

When I tried to backup my data before upgrading to 3.2, the standard backup from settings ended with a sad face and told me my media data could not be saved and I should look at a log file in /tmp/ for details. The log file states there was no space left on device.

I think such a common error case should be handled in a user friendly manner. Digging in log files should be reserved for more complex problems. ;-)

Related (but closed): Backup should warn for usage issues [not relevant]

When I tried to backup my data before upgrading to 3.2, the standard backup from settings ended with a sad face and told me my media data could not be saved and I should look at a log file in /tmp/ for details. The log file states there was no space left on device.

I think such a common error case should be handled in a user friendly manner. Digging in log files should be reserved for more complex problems. ;-)

Related (but closed): Backup should warn for usage issues [not relevant]

When I tried to backup my data before upgrading to 3.2, the standard backup from settings ended with a sad face and told me my media data could not be saved and I should look at a log file in /tmp/ for details. The log file states there was no space left on device.

--- edit -------------------

there was insufficient space on the internal memory, not on the target device (SD card)

mkdir: cannot create directory `/home/nemo/.local/share/system/privileged/Backups-tmp/units/sailfish_backup_2019-11-08T23-12-23Z/Media': no space left on device

--- /edit -------------------

I think such a common error case should be handled in a user friendly manner. Digging in log files should be reserved for more complex problems. ;-)

Related (but closed): Backup should warn for usage issues [not relevant]