GNU bug report logs - #55638
time-machine: backtrace about maybe-remove-expired-cache-entries

Previous Next

Full log

Message #17 received at 55638 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Maxime Devos <maximedevos <at> telenet.be>
Cc: 55638 <at> debbugs.gnu.org, zimoun <zimon.toutoune <at> gmail.com>
Subject: Re: bug#55638: time-machine: backtrace about
 maybe-remove-expired-cache-entries
Date: Sat, 28 May 2022 19:12:19 +0200

Hi,

Maxime Devos <maximedevos <at> telenet.be> 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’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.