On 26/07/2017 19:05, Colin Percival wrote:
> It means that tarsnap archived a file which was (allegedly) most recently
> modified before January 1st 1970. Why you have such a file is an open
> question, but it seems that these are more common than I expected; you're
> not the first person to trip
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/ccache/ccache_write.c, line 75.
> Abort
Hi
On 26. 07. 2017 12:38, 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/ccache/ccache_write.c, line 75.
>
