From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Mathieu Othacehe <othacehe@gnu.org>, 59784@debbugs.gnu.org
Subject: bug#59784: [version 1.4.0rc1] Retrying a failed install fails
Date: Sat, 17 Dec 2022 20:27:43 +0100 [thread overview]
Message-ID: <87zgblhlu8.fsf@pelzflorian.de> (raw)
In-Reply-To: <87v8magg6e.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sat, 17 Dec 2022 17:15:21 +0100")
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> The error message that’s haunting us:
>
> opening file `/gnu/store/….drv': No such file or directory
>
> comes from guix-daemon. It happens while the client is doing an
> ‘add-text-to-store’ RPC to add that .drv to the store.
> ‘LocalStore::addTextToStore’ supposedly creates the .drv file in
> /gnu/store and then reads it back (‘registerValidPath’ -> ‘addValidPath’
> -> ‘readDerivation’ -> ‘readFile’): this is where it gets ENOENT.
>
> It would suggest that the database is consistent, but that somehow
> writes don’t go through the overlay FS.
Most interesting.
I saw a comment
> void LocalStore::registerValidPaths(const ValidPathInfos & infos)
> {
> /* SQLite will fsync by default, but the new valid paths may not be fsync-ed.
> * So some may want to fsync them before registering the validity, at the
> * expense of some speed of the path registering operation. */
> if (settings.syncBeforeRegistering) sync();
In vain, I therefore tried
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: sync-before-registering.patch --]
[-- Type: text/x-patch, Size: 444 bytes --]
diff --git a/nix/libstore/globals.cc b/nix/libstore/globals.cc
index d4f9a46a74..5f8a3a3031 100644
--- a/nix/libstore/globals.cc
+++ b/nix/libstore/globals.cc
@@ -40,7 +40,7 @@ Settings::Settings()
reservedSize = 8 * 1024 * 1024;
fsyncMetadata = true;
useSQLiteWAL = true;
- syncBeforeRegistering = false;
+ syncBeforeRegistering = true;
useSubstitutes = true;
useChroot = false;
impersonateLinux26 = false;
[-- Attachment #3: Type: text/plain, Size: 43 bytes --]
But it changes nothing.
Regards,
Florian
next prev parent reply other threads:[~2022-12-17 19:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 17:52 bug#59784: [version 1.4.0rc1] Retrying a failed install fails pelzflorian (Florian Pelz)
2022-12-09 9:42 ` Ludovic Courtès
2022-12-09 11:11 ` Ludovic Courtès
2022-12-10 8:39 ` pelzflorian (Florian Pelz)
2022-12-13 9:40 ` Ludovic Courtès
2022-12-13 9:48 ` Ludovic Courtès
2022-12-13 22:22 ` pelzflorian (Florian Pelz)
2022-12-13 23:16 ` Ludovic Courtès
2022-12-14 13:36 ` pelzflorian (Florian Pelz)
2022-12-14 21:47 ` pelzflorian (Florian Pelz)
2022-12-14 23:50 ` Ludovic Courtès
2022-12-15 17:46 ` pelzflorian (Florian Pelz)
2022-12-15 20:44 ` pelzflorian (Florian Pelz)
2022-12-16 16:57 ` Ludovic Courtès
2022-12-16 20:28 ` pelzflorian (Florian Pelz)
2022-12-17 11:01 ` Ludovic Courtès
2022-12-17 19:36 ` pelzflorian (Florian Pelz)
2022-12-17 16:15 ` Ludovic Courtès
2022-12-17 19:27 ` pelzflorian (Florian Pelz) [this message]
2022-12-17 21:30 ` Ludovic Courtès
2022-12-18 0:23 ` Ludovic Courtès
2022-12-16 13:55 ` Maxime Devos
2022-12-16 20:17 ` pelzflorian (Florian Pelz)
2022-12-18 16:41 ` pelzflorian (Florian Pelz)
2022-12-12 12:07 ` pelzflorian (Florian Pelz)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zgblhlu8.fsf@pelzflorian.de \
--to=pelzflorian@pelzflorian.de \
--cc=59784@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=othacehe@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).