Article 5PQK0 Backup (rsync) -> [E] Error: rsync: [sender] write error: Broken pipe (32)

Backup (rsync) -> [E] Error: rsync: [sender] write error: Broken pipe (32)

by
JZL240I-U
from LinuxQuestions.org on (#5PQK0)
I do automatic backups via "backintime" after every boot up. Today I noticed a briefly shown popup with that message "[E] Error: rsync: [sender] write error: Broken pipe (32)". So I checked and found that this happened since october 2019 i.e. for all of my backups since then. *grrrr*

The disk is probably full:

Code:me@PC:~> df -h /backup
Dateisystem Groe Benutzt Verf. Verw% Eingehangt auf
/dev/sdc1 960G 860G 52G 95% /backupFirst question: Are these backups still usable or rather, how can I find out which files are not "kosher" anymore?

These backups also have a history. The disk that held them originally was dying, so I formatted a new one with ext4, same size partition, and "rsync -aXHAv"ed my backups over. The new disk is what throws the error now. I could enlarge this partition with gparted.

Now, I have more backup media. I checked the next:

Code:Failed to get take_snapshot log from None:
[Errno 2] No such file or directory: '/home/me/.local/share/backintime/takesnapshot_3.log'Ahmm, what? This is from the backintime utility which worked fine until now. What does that mean for my older backups? I just created a new one with no errors but now for all three users in the local home but with only one in the backup profile. What the...

Anyone with experience in such cases? Thanks in advance for sharing :).latest?d=yIl2AUoC8zA latest?i=sDQEE-FVtpY:71K5bG5wXfo:F7zBnMy latest?i=sDQEE-FVtpY:71K5bG5wXfo:V_sGLiP latest?d=qj6IDK7rITs latest?i=sDQEE-FVtpY:71K5bG5wXfo:gIN9vFwsDQEE-FVtpY
External Content
Source RSS or Atom Feed
Feed Location https://feeds.feedburner.com/linuxquestions/latest
Feed Title LinuxQuestions.org
Feed Link https://www.linuxquestions.org/questions/
Reply 0 comments