Subject: bug#55638: time-machine: backtrace about maybe-remove-expired-cache-entries

From: Ludovic Courtès <[email-masked]>
Date: Sat, 28 May 2022 19:12:19 +0200

Hi,

Maxime Devos <[email-masked]> skribis:

> It's a work-around, but there's still an underlying problem: 
> guix/cache.scm doesn't do 'fsync+rename', so the file is not created
> atomically, so in case of an abrupt shutdown or C-c at the wrong time,
> the file becomes corrupted without fault of the file system.

Right, I guess this is what we should fix first, by using
‘with-atomic-file-output’ for instance.

> As such, WDYT of making last-expiry-date more robust, by treating
> invalid contents as time=0 or something like that?

That too.

Ludo’.