On 07/19/16 23:40, Matthew Seaman wrote: > Ever since I upgraded my home system to: > > % freebsd-version -ku > 11.0-BETA1 > 11.0-BETA1 > > my nightly tarsnap backups have been behaving oddly. I'm seeing the > backup process take much longer, and it is generating a lot more network > traffic than previously.
Could you try comparing two consecutive archives? In particular I'm wondering if ZFS is presenting files in a different order when tarsnap lists directories... that would be annoying and would definitely increase the amount of traffic because it would break deduplication of tar headers. > I'm also getting a lot of error messages like this (repeated for each of > the ZFSes on this system.) > > Jul 19 19:00:00 lucid-nonsense backupsnap-zfs.sh[41680]: Created > snapshots zroot@20160719-1900 and children > Jul 19 19:00:00 lucid-nonsense backupsnap-zfs.sh[41680]: Backing up / > Jul 19 19:06:49 lucid-nonsense backupsnap-zfs.sh[41680]: tarsnap: .: > Unable to continue traversing directory tree: Not a directory > Jul 19 19:06:49 lucid-nonsense backupsnap-zfs.sh[41680]: Backing up /usr > Jul 19 19:58:26 lucid-nonsense backupsnap-zfs.sh[41680]: tarsnap: .: > Unable to continue traversing directory tree: Not a directory That's strange. Do you get this error when backing up an empty filesystem? -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid