From: pouya+lists.9fans@nohup.io
To: 9fans@9fans.net
Subject: [9fans] nfs timeouts
Date: Sun, 8 Aug 2021 11:55:10 +0100 [thread overview]
Message-ID: <9c41f4c5141474c19b1b7b09d8b5a1fa@nohup.io> (raw)
I recently set up NFS exports on a server on my local intranet. I can mount NFS directories after running nfs(4) but when I tried to do a small dircp(1) it invariably failed at the same point for each of the directories I tried:
term% nfs -p 666 -u /lib/ndb/glenda.passwd /lib/ndb/glenda.group somehost
term% mount -a /srv/somehost /n/somedir /somepath
term% dircp somelocaldir /somepath/someremotedir
[after a while...]
tar: error writing same/path/same/file: timeout
NetBSD, Linux, and macOS clients don't seem to have any issues.
Am I doing something wrong or does nfs(4) not work very well?
Thanks,
Pouya
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T060ac082dfe82490-M97f91963d4812f828e60d92e
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next reply other threads:[~2021-08-08 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-08 10:55 pouya+lists.9fans [this message]
2021-08-08 11:01 ` pouya+lists.9fans
2021-08-09 3:32 ` ori
2021-08-09 7:55 ` Steve Simon
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9c41f4c5141474c19b1b7b09d8b5a1fa@nohup.io \
--to=pouya+lists.9fans@nohup.io \
--cc=9fans@9fans.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.
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 NNTP newsgroup(s).