From: fsdfsdfsd3 via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 47706@debbugs.gnu.org
Subject: bug#47706: nfs mount in file-system works only if "nfs4" type is used for "mount" syscall
Date: Sun, 11 Apr 2021 08:33:34 +0000 [thread overview]
Message-ID: <Pgu6TXk6QaPqp_auy-Dl-BoHVRLiG4_00wVM_mPwSTaqUwEWRQ3-ur68EFQci8CaI8FZEw_X5h4clktJLvIDpMt81388osAVNL9idTUJk-Y=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 710 bytes --]
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!
[-- Attachment #2: Type: text/html, Size: 907 bytes --]
next reply other threads:[~2021-04-11 11:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-11 8:33 fsdfsdfsd3 via Bug reports for GNU Guix [this message]
2021-04-14 6:56 ` bug#47706: Acknowledgement (nfs mount in file-system works only if "nfs4" type is used for "mount" syscall) fsdfsdfsd3
2021-08-08 3:19 ` bug#47706: nfs mount in file-system works only if "nfs4" type is used for "mount" syscall Maxim Cournoyer
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='Pgu6TXk6QaPqp_auy-Dl-BoHVRLiG4_00wVM_mPwSTaqUwEWRQ3-ur68EFQci8CaI8FZEw_X5h4clktJLvIDpMt81388osAVNL9idTUJk-Y=@protonmail.com' \
--to=bug-guix@gnu.org \
--cc=47706@debbugs.gnu.org \
--cc=fsdfsdfsd3@protonmail.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.
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).