On 7/6/2018 6:18 PM, Les Mikesell wrote: > On Fri, Jul 6, 2018 at 1:38 PM, Bowie Bailey <[email protected]> wrote: >> Right now, the only error I've seen is the error that stopped the backup: >> rsync error: error in rsync protocol data stream (code 12) at io.c(1556) >> [generator=3.0.9.12] >> >> The main annoyance is that I have no way to track progress. While the >> backup is running, I can't tell if it's about to finish, or if it's >> bogged down and is likely to take a few more hours (or days). > Rsync probably builds a table in memory to track the inodes of files > with multiple links so you may be running out of RAM or slowing down > from swapping. For a brute-force approach to see what is happening > you could strace the rsync process on the sending side. You could at > least tell if it is still opening/reading files.
There was still plenty of free RAM and no swap usage. I know it was still doing something because the pool filesystem was slowly growing. I could try an strace, but I'll have to research that. I've never used strace before. -- Bowie ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ BackupPC-users mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
