[Burp-users] Stuck on Phase4 (shuffling)

[Moter P. <mot...@gm...>]

I've noticed backups for a particular host failing for several days now.
Logs show either:

2014-12-13 10:09:01: burp[27088] Begin phase4 (shuffle files)
2014-12-13 10:09:01: burp[27088] previous attempt started not hardlinked
2014-12-13 10:09:01: burp[27088]  not doing hardlinked archive
2014-12-13 10:09:01: burp[27088]  will generate reverse deltas
2014-12-13 10:09:01: burp[27088] Doing the atomic data jiggle...
2014-12-13 10:09:01: burp[27088] skipping already present file:
/pool2/backups/server/finishing/data/t/data/.blksnap/AAData.md
2014-12-13 10:09:01: burp[27088] to save log space, skips of other already
present files will not be logged
2014-12-13 10:50:49: burp[27088] zlib_inflate returned: -1
2014-12-13 10:50:49: burp[27088] error when inflating old file:
/pool2/backups/server/finishing/currentdup/data/t/home/someuser/archive/somefile.nsf
2014-12-13 10:50:51: burp[27088] could not finish up backup.
2014-12-13 10:50:51: burp[27088] Problem with prior backup. Please check
the client log on the server.


...or...

2014-12-22 00:49:01: burp[567] Begin phase4 (shuffle files)
2014-12-22 00:49:01: burp[567] previous attempt started not hardlinked
2014-12-22 00:49:01: burp[567]  not doing hardlinked archive
2014-12-22 00:49:01: burp[567]  will generate reverse deltas
2014-12-22 00:49:01: burp[567] Doing the atomic data jiggle...
2014-12-22 00:49:01: burp[567] skipping already present file:
/pool2/backups/server/finishing/data/t/data/.blksnap/AAData.md
2014-12-22 00:49:01: burp[567] to save log space, skips of other already
present files will not be logged
2014-12-22 01:40:28: burp[567] could not lstat
/pool2/backups/server/finishing/currentdup/data/t/home/someuser/archive/somefile.nsf
2014-12-22 01:40:28: burp[567] error when inflating old file:
/pool2/backups/server/finishing/currentdup/data/t/home/someuser/archive/somefile.nsf
2014-12-22 01:40:30: burp[567] could not finish up backup.
2014-12-22 01:40:30: burp[567] Problem with prior backup. Please check the
client log on the server.


I've seen a few topics on this previously.  One mentioned this was resolved
in an update (I'm running the latest 1.4.28 on both server and client).
Another mentioned trying setting the "directory_tree" option to 0 on the
server.  I have not tried this.  I have told burp to no longer compress the
file type in question but to no avail.

I'm dealing with a fairly large amount of data (4TB+) so each attempt is
fairly costly in terms of run time.  Any suggestions on untangling this?
I'd prefer to not to reset given how long it takes to take the initial base.