Usability problem: backup.sh assumes cwd has bulk storage space available

[byron-hawkins]

not device related

System info

Available disk space: 100GB on disk 1, 20GB on disk 2
Operating system: Fedora 38

---

Describe the issue below.

When backup.sh begins to pull data from the device, it stores everything in a directory ./backup-tmp, regardless of the backup directory selected by the user. It may be that the current directory is on a disk that does not have bulk storage space available, and that the selected backup directory is on some entirely different disk that does have space. In this case, backup will fail, even though space is available at the selected location. Note that Linux functions very poorly when the root filesystem runs out of disk space, potentially locking out the user.

Would it be possible to move backup-tmp over to the user's selected backup directory?

[mrrfv]

Would it be possible to move backup-tmp over to the user's selected backup directory?

Not at the moment, but there's a very easy workaround for that - just copy Open Android Backup's files (backup.sh and related) to the drive you want to store backup-tmp in.