Without some way to reproduce your problem, I'm at a loss to know what to suggest.
What about the 'rsync' process I mentioned?
I wonder why this 'rsync' process continued to run after the 'image-backup' process was terminated?In the "post-mortem":
1. ctrl-C yielded:2. checked ps; nothing found under 'image', but 'rsync' was "still busy"??:Code:
^Crsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at io.c(518) [generator=3.2.7]
Code:
$ ps -aux | grep rsyncroot 3591 0.0 0.2 143600 11584 ? D 05:17 0:04 rsync -aDH --partial --numeric-ids --delete --force --exclude /tmp/img-backup-mnt --exclude /dev --exclude /lost+found --exclude /media --exclude /mnt --exclude /proc --exclude /run --exclude /sys --exclude /tmp --exclude /var/swap --exclude /etc/udev/rules.d/70-persistent-net.rules --exclude /var/lib/asterisk/astdb.sqlite3-journal / /tmp/img-backup-mnt/
Statistics: Posted by irishmonk-57 — Sat Mar 09, 2024 6:19 pm