Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need rpc-statd started? #380

Closed
mathieubolla opened this issue May 21, 2019 · 5 comments
Closed

Need rpc-statd started? #380

mathieubolla opened this issue May 21, 2019 · 5 comments
Labels

Comments

@mathieubolla
Copy link

mathieubolla commented May 21, 2019

Description of issue/question

If I mount an NFS export on a macOS client, it is very slow to open any file for reading, showing the "color wheel of death", then eventually working fine.

On the OMV box logs, shows multiple:
kernel[259377.264975] lockd: cannot monitor some-redacted-local-client-hostname

Discovered here and there that doing this on server:
systemctl start rpc-statd
systemctl enable rpc-statd
(as root in SSH shell) fixes the issue.

Versions report

Client: macOS 10.13.6, last patch update (17G7024)
Server (extract from "Report"):

================================================================================
= OS/Debian information
================================================================================
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 9.9 (stretch)
Release: 9.9
Codename: stretch

================================================================================
= openmediavault information
================================================================================
Release: 4.1.22-1
Codename: Arrakis
@ryecoaaron
Copy link
Contributor

I don't have this problem on my five amd64 systems using nfs. Is this an arm board? If so, which one?

@votdev
Copy link
Member

votdev commented May 23, 2019

I do not find any resource that explicitly mention that rpc-statd is required to run NFS. I'm missing something?

@skarekrow
Copy link

AFAIK it's required for remote locks. Possibly required for NFSv4 as well?

@mathieubolla
Copy link
Author

Hi, sorry, didn't read about this issue for a while...

This is on a retired Dell Optiplex 360 (Intel CPU i7 870, pretty standard hardware)

The client is a recent Mac Book Pro, running up to date software

The resources didn't say it is required, but says it sometimes solve the problem. My experience here proved it to be true, albeit I have no idea why.

Here is part of a book I found recently stating that NFS on Mac needs rpc-statd to allow file locking. Maybe that's the mechanism at work in this issue? https://books.google.fr/books?id=zrI-U0KWj3cC&pg=PA454&lpg=PA454&dq=macos+rpc-statd&source=bl&ots=rFxwxLGtn-&sig=ACfU3U17qDHtAjRqH4D9VNyixLHzKE6Nrg&hl=fr&sa=X&ved=2ahUKEwiajo6StMjjAhUSExoKHXCLAaUQ6AEwCHoECAkQAQ#v=onepage&q=macos%20rpc-statd&f=false

Thanks,

Mathieu

votdev added a commit that referenced this issue Jul 26, 2019
Signed-off-by: Volker Theile <votdev@gmx.de>
@votdev votdev closed this as completed Jul 26, 2019
@votdev votdev added the 5.x label Jul 26, 2019
@votdev
Copy link
Member

votdev commented Jul 26, 2019

Fixed for OMV5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants