I've had a situation for a few weeks when trying to back up my home directory on TUMBLEWEED.
This in entirely new behaviour of rsync. I've been using this method for years to back up my home directory to a USB attached drive.
It starts out normally then just stops. It's claiming no space left on device when I finally hit CTRL-C because it's obviously stopped. It has 575.4 GB free of 931.3 GB.
The command I've always used is
Code:
rsync -av /home/flamebait /run/media/flamebait/BACKUP/flamebait/
This is the error I see when I do a CTRL-C
Code:
flamebait/.cache/google-chrome/Default/Cache/f_0b629a
^Crsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(636) [sender=3.1.2]
rsync: mkstemp "/run/media/flamebait/BACKUP/flamebait/flamebait/.15:46.png.u2GFyd" failed: Invalid argument (22)
rsync: mkstemp "/run/media/flamebait/BACKUP/flamebait/flamebait/.3:.jpg.12goj0" failed: Invalid argument (22)
rsync: mkstemp "/run/media/flamebait/BACKUP/flamebait/flamebait/.WTF?.jpg.uA71fA" failed: Invalid argument (22)
rsync: mkstemp "/run/media/flamebait/BACKUP/flamebait/flamebait/.flash.asp?id=84712.vzlotn" failed: Invalid argument (22)
rsync: rename "/run/media/flamebait/BACKUP/flamebait/flamebait/.cache/google-chrome/Default/Cache/.f_0988e9.6pWqiL" -> "flamebait/.cache/google-chrome/Default/Cache/f_0988e9": No space left on device (28)
How do I overcome this situation? This always used to work for backing up home. This is obviously new behaviour for me. I haven't been able to back op my /home for weeks and I'm getting nervous about no recent backups.
Bookmarks