[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#55638: time-machine: backtrace about maybe-remove-expired-cache-entr
From: |
Maxime Devos |
Subject: |
bug#55638: time-machine: backtrace about maybe-remove-expired-cache-entries |
Date: |
Thu, 26 May 2022 17:12:18 +0200 |
User-agent: |
Evolution 3.38.3-1 |
Ludovic Courtès schreef op do 26-05-2022 om 17:05 [+0200]:
> This file was empty when you ran the command instead of containing an
> integer (could have been a file system corruption or something like
> that).
>
> Solution:
>
> rm ~/.cache/guix/inferiors/last-expiry-cleanup
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.
As such, WDYT of making last-expiry-date more robust, by treating
invalid contents as time=0 or something like that?
Greetings,
Maxime.
signature.asc
Description: This is a digitally signed message part