After a period of successful backups under SME 8, I upgraded to 9.2 about two weeks ago
Incremental backup was working (though I had accidentally configured it for 17 incremental backups per set!) until 6/15 (last Friday) when it failed - still doing incrementals...
==================================
DAILY BACKUP TO WORKSTATION REPORT
==================================
Backup of spencer.barnlea.com started at Fri Jun 15 23:35:04 2018
Destination //degas.fawnroad/home/pub/spencer.barnlea.com/set1
Basename inc-011-20180615233504
Starting the backup with a timeout of 7 hours
*** No backup allowed or error during backup ***
Failed to add set /mnt/smb/spencer.barnlea.com/set1/inc-011-20180615233504 to catalog. No child processes
A manually triggered full backup also failed...
==================================
DAILY BACKUP TO WORKSTATION REPORT
==================================
Backup of spencer.barnlea.com started at Sun Jun 17 10:32:53 2018
Destination //degas.fawnroad/home/pub/spencer.barnlea.com/set2
Basename full-20180617103253
Starting the backup with a timeout of 24 hours
--------------------------------------------
356903 inode(s) saved
including 414 hard link(s) treated
0 inode(s) changed at the moment of the backup and could not be saved properly
0 byte(s) have been wasted in the archive to resave changing files
0 inode(s) not saved (no inode/file change)
0 inode(s) failed to be saved (filesystem error)
301 inode(s) ignored (excluded by filters)
0 inode(s) recorded as deleted from reference backup
--------------------------------------------
Total number of inode(s) considered: 357204
--------------------------------------------
EA saved for 0 inode(s)
--------------------------------------------
*** No backup allowed or error during backup ***
Failed to add set /mnt/smb/spencer.barnlea.com/set1/inc-011-20180615233504 to catalog. No child processes
An Internet search on the "Failed to add set to catalog" message brought me to a discussion between developers back in 2014...
https://bugs.contribs.org/show_bug.cgi?id=8610 but the issue was slightly different to mine (I'm backing up to a an NFS share, not a USB stick), and I saw no clear resolution to it that seemed helpful.
Could somebody point me in the right direction to resolve this, please?