Finally I've fixed the Ubuntu problem. Obviously your script doesn't work properly with this subdirectory:It's the image file that is out of space, not the device it resides on. You specify the size of that image file when prompted for "Initial image file ROOT filesystem size (MB)". If you're accepting the default (estimated) value, it may be too small. Have you tried a considerably larger value? Do you have external storage mounted somewhere other than /media and/or /mnt which image-backup would be including in the backup?
Code:
/var/lib/snapd/snaps/Code:
rsync: [receiver] write failed on "/tmp/img-backup-mnt/var/lib/snapd/snaps/gnome-42-2204_174.snap": No space ....rsync error: error in file IO (code 11) at receiver.c(380) [receiver=3.2.7]rsync: [sender] write error: Broken pipe (32)rsync error: error in file IO (code 11) at io.c(848) [sender=3.2.7]Before snaps deletion your script asked this:
Code:
Initial image file ROOT filesystem size (MB) [21970]? 25000Code:
Initial image file ROOT filesystem size (MB) [21551]? 25000One way or another, the snaps deletion fixes this problem. Now backup image is created without any errors.
It would be ideally, if your script will detect /snaps presence and ask if user wishes to back it up or exclude it from backup for the sake of space economy.
Would you mind to do it?
Statistics: Posted by DeadlineX — Tue Dec 24, 2024 3:33 am