GNU bug report logs - #47706
nfs mount in file-system works only if "nfs4" type is used for "mount" syscall

Previous Next

Full log

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

From: fsdfsdfsd3 <fsdfsdfsd3 <at> protonmail.com>
To: "bug-guix <at> gnu.org" <bug-guix <at> gnu.org>
Subject: nfs mount in file-system works only if "nfs4" type is used for
 "mount" syscall
Date: Sun, 11 Apr 2021 08:33:34 +0000

[Message part 1 (text/plain, inline)]

Hello,

I ran into an issue with trying to mount an nfs file-system in an operating-system config.. I managed to trace it back to being an issue with the mount syscall.

The following did not work:
(mount "192.168.1.10:/nas-server" "/mnt/nas-client" "nfs" 0 "addr=192.168.
1.10")
and would result in an error "No route to host"

I changed the type from "nfs" to "nfs4" however and this did work (For context; at the command line, both mount.nfs and mount.nfs4 also work fine., mount.nfs also works fine without nfs-utils installed).

This might be fixable by adding another check-procedure option for "nfs4" in addition to nfs, but I am sending it your way in case there is something else going on.

Thank you!

[Message part 2 (text/html, inline)]

Previous Next

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