The job completed OK. Thanks again.
> On Dec 12, 2017, at 1:50 PM, Steve Palm <n9...@n9yty.com> wrote:
>
> It is running now, it's a large-ish host, so it will take a while, but it is
> looking good.
>
> Thanks!
>
>> On Dec 12, 2017, at 1:34 PM, Craig Barratt via BackupPC-devel
>> <backuppc-devel@lists.sourceforge.net
>> <mailto:backuppc-devel@lists.sourceforge.net>> wrote:
>>
>> I pushed a change ba50ec9
>> <https://github.com/backuppc/rsync-bpc/commit/ba50ec9fdda2429d6afc812d80ab65f4c9d08d5b>
>> that checks the hlink_nlinks hash is non-NULL before accessing it. Can you
>> try that change, either by apply that diff, or building rsync_bpc with the
>> latest 3.0.9 branch, eg:
>>
>> git clone https://github.com/backuppc/rsync-bpc
>> <https://github.com/backuppc/rsync-bpc>
>> cd rsync-bpc
>> git checkout 3.0.9
>> ./configure
>> make
>> sudo make install
>>
>> On Tue, Dec 12, 2017 at 10:53 AM, Steve Palm <n9...@n9yty.com
>> <mailto:n9...@n9yty.com>> wrote:
>>
>> On Dec 3, 2017, at 10:28 PM, Craig Barratt via BackupPC-devel
>> <backuppc-devel@lists.sourceforge.net
>> <mailto:backuppc-devel@lists.sourceforge.net>> wrote:
>>> BackupPC 4.1.5 <https://github.com/backuppc/backuppc/releases/tag/4.1.5>
>>> has been released on Github.
>>>
>>> New versions of BackupPC-XS 0.57
>>> <https://github.com/backuppc/backuppc-xs/releases/tag/0.57> and rsync-bpc
>>> 3.0.9.9 <https://github.com/backuppc/rsync-bpc/releases/tag/3.0.9.9> have
>>> also been released. BackupPC 4.1.5 requires BackupPC-XS 0.57.
>>
>> I'm seeing new errors on hosts that were working before. I am on 4.1.5,
>> with BackupPC-XS-0.57 and rsync-bpc 3.0.9.10 as that was the latest release
>> on Github. Should I revert to rsync-bpc-3.0.9.9?
>>
>> Errors below, not sure where to look:
>>
>> Backup prep: type = incr, case = 4, inPlace = 0, doDuplicate = 0, newBkupNum
>> = 2998, newBkupIdx = 8, lastBkupNum = 2997, lastBkupIdx = 7 (FillCycle = 0,
>> noFillCnt = 6)
>> Running: /usr/local/bin/rsync_bpc --bpc-top-dir /mnt/stage/BackupPC
>> --bpc-host-name dasco --bpc-share-name / --bpc-bkup-num 2998 --bpc-bkup-comp
>> 1 --bpc-bkup-prevnum 2997 --bpc-bkup-prevcomp 1 --bpc-bkup-inode0 643528
>> --bpc-attrib-new --bpc-log-level 1 -e /usr/bin/ssh\ -T\ -q\ -x\ -l\
>> backuppc\ -c\ arcfour --rsync-path=nice\ -n\ 10\ sudo\ /usr/bin/rsync
>> --super --recursive --numeric-ids --perms --owner --group -D --times --links
>> --hard-links --delete --partial --log-file-format=log:\ %o\ %i\ %B\ %8U,%8G\
>> %9l\ %f%L --stats --one-file-system --timeout=72000 --exclude=/proc
>> --exclude=/nfs hostname_here:/ /
>> incr backup started for directory /
>> Xfer PIDs are now 14182
>> This is the rsync child about to exec /usr/local/bin/rsync_bpc
>> rsync_bpc exited with fatal status 0 (139) (This is the rsync child about to
>> exec /usr/local/bin/rsync_bpc)
>> Xfer PIDs are now
>> Got fatal error during xfer (rsync_bpc exited with fatal status 0 (139)
>> (This is the rsync child about to exec /usr/local/bin/rsync_bpc))
>> Backup aborted (rsync_bpc exited with fatal status 0 (139) (This is the
>> rsync child about to exec /usr/local/bin/rsync_bpc))
>> BackupFailCleanup: nFilesTotal = 0, type = incr, BackupCase = 4, inPlace =
>> 0, lastBkupNum = 2997
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org <http://slashdot.org/>!
>> http://sdm.link/slashdot <http://sdm.link/slashdot>
>> _______________________________________________
>> BackupPC-devel mailing list
>> BackupPC-devel@lists.sourceforge.net
>> <mailto:BackupPC-devel@lists.sourceforge.net>
>> List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel
>> <https://lists.sourceforge.net/lists/listinfo/backuppc-devel>
>> Wiki: http://backuppc.wiki.sourceforge.net
>> <http://backuppc.wiki.sourceforge.net/>
>> Project: http://backuppc.sourceforge.net/ <http://backuppc.sourceforge.net/>
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org <http://slashdot.org/>!
>> http://sdm.link/slashdot_______________________________________________
>> <http://sdm.link/slashdot_______________________________________________>
>> BackupPC-devel mailing list
>> BackupPC-devel@lists.sourceforge.net
>> <mailto:BackupPC-devel@lists.sourceforge.net>
>> List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel
>> Wiki: http://backuppc.wiki.sourceforge.net
>> Project: http://backuppc.sourceforge.net/
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org!
> http://sdm.link/slashdot_______________________________________________
> BackupPC-devel mailing list
> BackupPC-devel@lists.sourceforge.net
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel
> Wiki: http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-devel mailing list
BackupPC-devel@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
