From: Fredrik Salomonsson <plattfot@posteo.net>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Trouble with nfs mount
Date: Mon, 17 Oct 2022 16:49:18 +0000 [thread overview]
Message-ID: <875ygifl9t.fsf@d2.com> (raw)
In-Reply-To: <871qr7z0fx.fsf@gmail.com>
Hi,
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> Hi,
>
> Fredrik Salomonsson <plattfot@posteo.net> writes:
>
> [...]
>
>> ---✂----------------------------------------------------------------------------
>> …
>> shepherd: Evaluating user expression (and (defined? (quote transient?)) (map (# ?) ?)).
>> guix system: warning: exception caught while executing 'start' on service 'file-system-/media/Valhalla':
>> In procedure mount: mount "fafner:/srv/nfs4/Valhalla" on "///media/Valhalla": Invalid argument
>> guix system: warning: some services could not be upgraded
>> …
>> --------------------------------------------------------------------------------
>>
>> So that's probably what's happening during boot.
>>
>> I have no idea how it transforms the mount-point from "/media/Valhalla"
>> to "///media/Valhalla" and if that's a red herring.
>>
>> Any ideas what I'm doing wrong?
>
> Nothing; mounting an NFS file system at boot is not supported currently
> with Guix System; see the related issue #47706.
Ah, ok. Thanks for the info.
> My current ugly workaround is to define the mount points with "(mount?
> #f)" and mount them via a script post boot, e.g.:
>
> --8<---------------cut here---------------start------------->8---
> (file-system
> (device "jami-buildmachine-04:/srv/nfs/jami")
> (mount-point "/var/cache/jami")
> (create-mount-point? #t)
> (type "nfs")
> (mount? #f)
> (options "soft,user"))
> --8<---------------cut here---------------end--------------->8---
Yeah, I think I'll just add a shepherd service to my home configuration
that mounts and unmounts my NFS device until this is resolved.
--
s/Fred[re]+i[ck]+/Fredrik/g
prev parent reply other threads:[~2022-10-17 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 21:46 Trouble with nfs mount Fredrik Salomonsson
2022-10-16 23:17 ` Felix Lechner via
2022-10-17 1:08 ` Fredrik Salomonsson
2022-10-17 1:18 ` Felix Lechner via
2022-10-17 16:37 ` Fredrik Salomonsson
2022-10-17 16:50 ` Remco
2022-10-23 20:39 ` Fredrik Salomonsson
2022-10-17 1:46 ` Maxim Cournoyer
2022-10-17 16:49 ` Fredrik Salomonsson [this message]
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=875ygifl9t.fsf@d2.com \
--to=plattfot@posteo.net \
--cc=help-guix@gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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.
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).