GNU bug report logs - #75209
30.0.93; Emacs reader failed to read data in "/home/nlj/.cache/org-persist/gc-lock.eld"

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ihor Radchenko <yantar92 <at> posteo.net>
Cc: 75209 <at> debbugs.gnu.org, njackson <at> posteo.net
Subject: Re: bug#75209: 30.0.93; Emacs reader failed to read data in
 "/home/nlj/.cache/org-persist/gc-lock.eld"
Date: Fri, 07 Mar 2025 21:12:10 +0200

> From: Ihor Radchenko <yantar92 <at> posteo.net>
> Cc: Eli Zaretskii <eliz <at> gnu.org>, 75209 <at> debbugs.gnu.org
> Date: Fri, 07 Mar 2025 16:50:24 +0000
> 
> Ihor Radchenko <yantar92 <at> posteo.net> writes:
> 
> >>   2025-02-20 22:11:55.058196 Gnus leaving org-persist--refresh-gc-lock normally:
> >>   Timer: org-persist--refresh-gc-lock (nil)
> >>   Due: In 3599.970393228 s (26551 64779 28641 22000)
> >>   Triggered: t		Integral Multiple: nil
> >>   Repeat Delay: 3600	Idle Delay: nil
> >
> > This looks like the most recent write to the lock file.
> >
> > The one at 6am happens after the failing read at 06:46:07.188999.
> >
> > On the other hand, it is just a fraction of second apart.
> > Is `insert-file-contents' atomic operation?
> 
> Eli, do you have any idea if `insert-file-contents' may be affected by
> the inserted file being written simultaneously?

Emacs reads the file in chunks, so I think the answer depends on the
filesystem.

Previous Next

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