On 05/29/2017 09:24 PM, Tim Evans wrote:

Today's update: The full backup ran for just a few minutes over 24 hours and was killed by BackupPC; log says:

2017-05-29 15:34:24 Backup failed on pelican (BackupPC_tarExtract exited with fail status 256)

2017-05-29 15:34:27 Started full backup on pelican (pid=15026, share=C$)

As you can see, a new full backup was kicked off almost immediately.

I've googled the "BackupPC_tarExtract exited with fail status 256" message and found many hits, going back to version 3 of BackupPC. Seems to be a problem with Linux 'tar' extracting the incoming data.

There was a thread just a month ago (late April/early May) on this mailing list entitled "Multiple issues on newly installed 4.1.0" which discussed the apparent same issue of failing backups due to a problem in 'tar.' In this thread, Craig Barratt wrote that he had pushed a fix to git for this issue. I'm guessing this hasn't yet made it into the 4.1.2 version in the Hobbes Fedora 25 repo?

Any other info would be appreciated.  Thanks.

--
Tim Evans                       |5 Chestnut Court
443-394-3864                    |Owings Mills, MD 21117

------------------------------------------------------------------------------
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
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/