rson to trip over this (the assertion is new in 1.0.38).
Hmmm... the oldest files in the zfs where the abort trap occurred date
back to 2007.
However it does seem pkg(8) fills up /var/cache/pkg with files mostly
dated at the epoch, but with a few like this:
# ls -la /var/cache/pkg/p5-File
On 07/26/17 03:37, Matthew Seaman wrote:
> So, I had one instance of this during last night's backups:
>
> backupsnap-zfs.sh[18449]: Assertion failed: ((ccr->mtime >= 0) &&
> ((uintmax_t)ccr->mtime <= UINT64_MAX)), function callback_write_rec,
> file tar/ccac
tar/ccache/ccache_write.c, line 75.
> Abort trap
I've never seen this with tarsnap, but I used to regularly see warnings
about files with negative mtimes with Duplicity [1] (on Linux, ext4).
It's not necessarily something wrong with your zfs. It's probably just
some files copied over from a dif
