From: Mi Jinlong <mijinlong@cn.fujitsu.com>
To: hce <webmail.hce@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: mac error
Date: Fri, 14 Jan 2011 10:37:40 +0800 [thread overview]
Message-ID: <4D2FB6F4.6070304@cn.fujitsu.com> (raw)
In-Reply-To: <AANLkTin04TeswNAM89ij84YzfeTAR7rsppGyZFfq01qM@mail.gmail.com>
hce :
> Hi,
>
> I am running nfs server on a CentOS 5, it works fine for all
> connections from linux, windows clients. Mac clients worked fine for
> coping some regular files, but it could not copy mac packaging file
> with the extension *.dmg, it stuck with an error "nfs server lockd not
> responding", at the same time the server got a log message of
> "rpc.statd[2448]: Can't callback linux_server (100021,4), giving up".
>
> Appreciate advice what could cause that problem and how could fix it?
Hi hce,
You use NFSv3,
the NFSv3's file lock service depend on NLM(Network Lock Manager),
that need a user space program named rpc.statd to support service
like this:
| nfs client | nfs server
-------------------------------------------------
| |
user space | rpc.statd <---> rpc.statd
| ^ | ^
--------------------|------------------------|----
| v | v
kernel | lockd <---> lockd
when your nfs client is a MAC, maybe Mac's user space don't support
a program as rpc.statd, or you don't make the program run correctly.
Maybe you can use NFSv4 to avoid this problem.
--
----
thanks
Mi Jinlong
next prev parent reply other threads:[~2011-01-14 2:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 1:13 mac error hce
2011-01-14 2:37 ` Mi Jinlong [this message]
2011-01-14 4:01 ` hce
2011-01-14 6:02 ` Mi Jinlong
2011-01-14 6:24 ` hce
2011-01-14 15:18 ` Chuck Lever
2011-01-14 15:55 ` peter.staubach
2011-01-14 17:00 ` Chuck Lever
2011-01-16 22:09 ` hce
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=4D2FB6F4.6070304@cn.fujitsu.com \
--to=mijinlong@cn.fujitsu.com \
--cc=linux-nfs@vger.kernel.org \
--cc=webmail.hce@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