[SOLVED] Backup Erroneously Reporting Insufficient Space.

[gfngfn256]

So this should do the trick:

Firstly - delete the data currently in /mnt/usb-backup leaving the directory there empty.

Then:

nano /etc/fstab

#add the following line, save & exit

UUID=7751d33a-13dc-45f2-83b3-49016c708672 /mnt/usb-backup ext4 defaults,nofail 0 2

# ctrl-x, y, enter, to save

mount -a

Good luck.

(Always remember, that with a backup target that depends on a mounted externally attached device, if that device is unavailable, your mountpoint will still be the target for the backup locally, & eventually filling up your disk!).

 

[dCipher]

I re-mounted the USB drive and used the Stop mode for backup and now everything works. The problem with the /mnt/usb-backup happened when I disconnected the USB drive for safe keeping. Coming from a Windows background I thought I could just plug it in again and everything would work. I want to thank everyone for their help. I have learned a lot more about Linux and I will try not to bother anyone again for a long time .

 

[gfngfn256]

I will try not to bother anyone again for a long time

Another difference between Windows & Linux is that Linux guys enjoy being bothered!

Anyway - happy you got sorted maybe mark this thread as Solved. At the top of the thread, choose the Edit thread button, then from the (no prefix) dropdown choose Solved.

Happy Proxmoxing!

 

[Impact]

The /etc/fstab could look like this

# backup
UUID=7751d33a-13dc-45f2-83b3-49016c708672 /mnt/usb-backup ext4 defaults,nofail 0 2

Before you mount it (via mount -av) I'd suggest you run this

# Delete the old data
rm -rf /mnt/usb-backup

# Create mount path and make it unwritable so this doesn't happen again
mkdir -p /mnt/usb-backup
chattr +i /mnt/usb-backup

The chattr is for this. The nofail is to prevent boot failures when the disk isn't attached.

Edit: I was too slow.

 

[gfngfn256]

chattr -+ /mnt/usb-backup

I believe that should be:

chattr +i /mnt/usb-backup

The +i will make the file immutable, as shown here.

 

[Impact]

Thanks. Yeah I also messed up the link describing it but it's fixed now.