From: "Sébastien Lerique" <sl@eauchat.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: “guix gc”, auto gcroots, cluster deployments
Date: Mon, 10 May 2021 22:40:28 +0900 [thread overview]
Message-ID: <874kfa671v.fsf@eauchat.org> (raw)
In-Reply-To: <87im3qq57z.fsf@elephly.net>
Hi Ricardo, all,
On 10 May 2021 at 18:59, Ricardo Wurmus <rekado@elephly.net>
wrote:
> On my cluster installation I ran “guix gc --list-dead” out of
> curiosity. When
> finding roots, the daemon also removes what it considers stale
> links. On my
> cluster installation not all links always resolve, because the
> target files
> reside on remote file systems. These remote locations are not
> readable by the
> root user on the server where guix-daemon runs (ignoring local
> root
> privileges is pretty common for NFS servers), so they cannot
> possibly be
> resolved.
Please excuse my hijacking this thread: I have been trying out
configurations to get Guix working on the cluster I have access
to, without root access for the daemon, and one problem I ran into
is a curious bug when the store is on an NFS share. See
https://lists.gnu.org/archive/html/guix-science/2021-03/msg00010.html
(Case 3).
In your setup, is the store on an NFS share? If so, did you do
anything special to get that working?
Best,
Sébastien
next prev parent reply other threads:[~2021-05-10 13:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 9:59 “guix gc”, auto gcroots, cluster deployments Ricardo Wurmus
2021-05-10 10:59 ` Roel Janssen
2021-05-10 11:59 ` Ricardo Wurmus
2021-05-10 15:45 ` Roel Janssen
2021-05-10 16:23 ` Ricardo Wurmus
2021-05-11 20:42 ` Ludovic Courtès
2021-05-10 13:40 ` Sébastien Lerique [this message]
2021-05-10 13:59 ` Guix on NFS Ricardo Wurmus
2021-05-11 20:50 ` “guix gc”, auto gcroots, cluster deployments Ludovic Courtès
2021-05-14 10:21 ` Ricardo Wurmus
2021-06-08 12:55 ` Ludovic Courtès
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=874kfa671v.fsf@eauchat.org \
--to=sl@eauchat.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).