Bug #25560
Allow nfs onestart to work with NFSv4
Seen in:
Sprint:
Severity:
New
Backlog Priority:
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No
Description
I've had a few problems with disk encryption and NFS starting on boot, so I set the service to be started manually, which I do after entering the disk encryption key.
Unchecking "Start on boot" causes NFS 4 to not run when starting it manually. Mounting fails with:
mount_nfs -o tcp -o soft -o bg -o vers=4 freenas.local:/mnt/data/test test_nfs
mount_nfs: can't mount /mnt/data/test from freenas.local onto /Users/andsens/Workspace/appliances/FreeNAS/test_nfs: RPC prog. not avail
Once I enable the service to start on boot and then restart the service, everything mounts fine.
Running
sudo sh -c '(source /etc/rc.conf.local; echo $nfsv4_server_enable)'
yields only "YES" when that checkmark is set and
rpcinfo -p localhost
always only lists versions 2 & 3, but I believe that is because v4 doesn't need rpcbind.
I'm not sure which of the details above are relevant so I just put them all in there.
Associated revisions
fix(middlewared/service): allow nfs onestart to work with NFSv4
Ticket: #25560
(cherry picked from commit aeaf96bf37bc7ea7656b69c2173a04079e3db480)
History
#1
Updated by Dru Lavigne about 1 year ago
Updated by Dru Lavigne - Assignee changed from Release Council to William Grzybowski
#2
Updated by William Grzybowski about 1 year ago
Updated by William Grzybowski - Status changed from Unscreened to Screened
- Priority changed from No priority to Expected
- Target version set to 11.1
Updated by Nick Wolff
fix(middlewared/service): allow nfs onestart to work with NFSv4
Ticket: #25560