unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Fredrik Salomonsson <plattfot@posteo.net>
To: help-guix <help-guix@gnu.org>
Subject: Trouble with nfs mount
Date: Sun, 16 Oct 2022 21:46:29 +0000	[thread overview]
Message-ID: <87k04ze91m.fsf@posteo.net> (raw)

Hi Guix,

I'm having some issues with my nfs storage on Guix System.

Here is the part of my configuration that deals with mounting the nfs
device.

  (define nfs-valhalla
    (file-system
     (device "fafner:/srv/nfs4/Valhalla")
     (mount-point "/media/Valhalla")
     (options "auto,_netdev,timeo=10")
     (type "nfs4")
     (mount? #f)
     (check? #f)))

  (operating-system
   ;; …
   (file-systems
    (cons*
     ;; …
     nfs-valhalla
     %base-file-systems)))

cat /etc/fstab:
---✂----------------------------------------------------------------------------
  …
  fafner:/srv/nfs4/Valhalla	/media/Valhalla	nfs4	auto,_netdev,timeo=10	
--------------------------------------------------------------------------------

As you can see Guix creates it just fine in /etc/fstab. I can manually
mount it. But if it's mounted when I'm shutting down the system it will
block. Sheperd will wait for some process to finish (which I assume is
the nfs mount). It works fine if I manually unmount it before shutting
down.

If I set it to mount on boot, it wont reach the tty prompt. Instead it
will get stuck somewhere along the boot process (grub menu to the
rescue). I do see shepherd failing to mount it after I've run guix
system reconfigure.

---✂----------------------------------------------------------------------------
…
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?

Thanks!

-- 
s/Fred[re]+i[ck]+/Fredrik/g


             reply	other threads:[~2022-10-16 21:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16 21:46 Fredrik Salomonsson [this message]
2022-10-16 23:17 ` Trouble with nfs mount 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

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=87k04ze91m.fsf@posteo.net \
    --to=plattfot@posteo.net \
    --cc=help-guix@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.
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).