From: steve <steve@steve-ss.com>
To: linux-nfs@vger.kernel.org
Subject: nfs3 lockd: cannot monitor errors
Date: Sat, 03 Mar 2012 13:21:08 +0100 [thread overview]
Message-ID: <4F520CB4.1030203@steve-ss.com> (raw)
Hi
We recently switched to nfs3 from nfs4 and now we're getting lots of
lockd errors. We can remove the error by mounting with:
-o local_lock=posix
We had to switch to be able to use the posix acl we had set on the share.
What problems may we face by setting the local_lock?
Thanks,
Steve
next reply other threads:[~2012-03-03 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 12:21 steve [this message]
2012-03-05 23:16 ` nfs3 lockd: cannot monitor errors steve
2012-03-05 23:23 ` Chuck Lever
2012-03-06 7:46 ` steve
2012-03-06 16:12 ` Chuck Lever
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=4F520CB4.1030203@steve-ss.com \
--to=steve@steve-ss.com \
--cc=linux-nfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.