Dan: >> to get pxeboot to do v3, add to /boot/loader.conf >> boot-nfsroot-options=“nfsv3” Thanks. I'm using grub for the bootloader and menu, and comparable entry should be: set kfreebsd.boot.nfsroot.options="nfsv3" It does not work however. mount_root hangs for a while then reverts to V2. I've asked about this on the grub-devel list, and will share the answer here.
Rick: Would it be worth trying to pass a nolockd option for this? As you had stated in another thread, "For NFSv3 mounts, I'd suggest the nolockd option, unless you have multiple clients concurrently doing byte range locking on the same file. (With "nolockd" option on the mounts, you shouldn't need to run rpc.lockd, rpc.statd and that implies NFSLOCKD shouldn't be needed, too.)" Should I try this? If yes, how is it done? >> Just fyi, "hard" is the default and "intr" is an alternative to "hard", so >> I'm not sure what you get when specifying both? You should choose one or the >> other. (You will get "hard" for the first 2 entries.) Thanks. Corrected by removing both. Konstantin: Have not gotten around to trying the code yet and thanks. ----- FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/Some-NFS-server-V4-questions-tp5959433p5959686.html Sent from the freebsd-current mailing list archive at Nabble.com. _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
