Re: Some NFS server V4 questions
Kostik wrote: > On Sun, Oct 26, 2014 at 06:42:29PM -0400, Rick Macklem wrote: > > Worked fine for me. Do you mind if I commit this or would you > > rather > > do it. > > I committed the change as r273727. > > One issue with the commit is the specified MFC. The change will > compile > on stable/10, but as far as I remember the state of sysctl patches, > it is nop on 10. It can be made functional with more patches to > nfsserver, but I prefer for the functionality to wait the needed MFCs > in > kern_sysctl.c. Righto. Thanks. I think the workaround of "build a kernel with options NFSD" (which most GENERIC kernels have) will be sufficient for now. Thanks again, rick ps: Now I know what TUN means;-) > ___ > 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" > ___ 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"
Re: Some NFS server V4 questions
On Sun, Oct 26, 2014 at 06:42:29PM -0400, Rick Macklem wrote: > Worked fine for me. Do you mind if I commit this or would you rather > do it. I committed the change as r273727. One issue with the commit is the specified MFC. The change will compile on stable/10, but as far as I remember the state of sysctl patches, it is nop on 10. It can be made functional with more patches to nfsserver, but I prefer for the functionality to wait the needed MFCs in kern_sysctl.c. ___ 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"
Re: Some NFS server V4 questions
Kostik wrote: > On Sun, Oct 26, 2014 at 08:14:05AM -0400, Rick Macklem wrote: > > Beeblebrox wrote: > > > Sorry guys, we have a considerable time-zone difference. > > > > > > >> It appears that the sysctl must be set before mountd, nfsd are > > > >> started to take effect. (Or they must be restarted after it is > > > >> set.) > > > I had apparently re-started nfsd but not mountd. This time > > > re-starting both and launching the PXE client fails at mount_root > > > stage as expected: > > > exec /sbin/init: error 43 > > > exec /rescue/init: error 43 > > > panic: no init > > > > > > One cannot set "sysctl vfs.nfsd.server_min_nfsvers=4" until one > > > of > > > mountd/nfsd is started however, otherwise it gives an error. I > > > have > > > not tried, but I suppose this error does not happen when placeed > > > in > > > /etc/sysctl.conf? > > > sysctl: unknown oid 'vfs.nfsd.server_min_nfsvers': No such file > > > or > > > directory > > > > > It works if it is /etc/sysctl.conf if "options NFSD" are specified > > for the kernel, which is what GENERIC for i386 has. > > > > If "options NFSD" isn't in your kernel config, I think you'd have > > to > > get nfsd.ko loaded before setting the sysctl and do both before > > starting mountd. > > > > I don't know of a clean way to do this? > > > > Putting kldload and sysctl command lines in mountd_precmd() in > > /etc/rc.d/mountd would do it I suspect. Maybe rc variables for > > this should be added? (I haven't tried this since the only > > kernels I have handy have "options NFSD" in them.) > > With the following patch, the same variables should work when > set from the loader.conf (i.e. pre-boot) or using kenv(8). > > diff --git a/sys/fs/nfsserver/nfs_nfsdkrpc.c > b/sys/fs/nfsserver/nfs_nfsdkrpc.c > index d2145cc..4fb9c93 100644 > --- a/sys/fs/nfsserver/nfs_nfsdkrpc.c > +++ b/sys/fs/nfsserver/nfs_nfsdkrpc.c > @@ -85,16 +85,16 @@ SYSCTL_DECL(_vfs_nfsd); > SVCPOOL *nfsrvd_pool; > > static int nfs_privport = 0; > -SYSCTL_INT(_vfs_nfsd, OID_AUTO, nfs_privport, CTLFLAG_RW, > +SYSCTL_INT(_vfs_nfsd, OID_AUTO, nfs_privport, CTLFLAG_RWTUN, > &nfs_privport, 0, > "Only allow clients using a privileged port for NFSv2 and 3"); > > static int nfs_minvers = NFS_VER2; > -SYSCTL_INT(_vfs_nfsd, OID_AUTO, server_min_nfsvers, CTLFLAG_RW, > +SYSCTL_INT(_vfs_nfsd, OID_AUTO, server_min_nfsvers, CTLFLAG_RWTUN, > &nfs_minvers, 0, "The lowest version of NFS handled by the > server"); > > static int nfs_maxvers = NFS_VER4; > -SYSCTL_INT(_vfs_nfsd, OID_AUTO, server_max_nfsvers, CTLFLAG_RW, > +SYSCTL_INT(_vfs_nfsd, OID_AUTO, server_max_nfsvers, CTLFLAG_RWTUN, > &nfs_maxvers, 0, "The highest version of NFS handled by the > server"); > > static int nfs_proc(struct nfsrv_descript *, u_int32_t, SVCXPRT > *xprt, Worked fine for me. Do you mind if I commit this or would you rather do it. Thanks, rick > ___ > 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" > ___ 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"
Re: Some NFS server V4 questions
Beeblebrox wrote: 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=3D"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. > I'm not sure. I vaguely recall that pxeboot (which is a stripped down version of "boot") uses NFS to read /boot/loader.conf. I'd try putting it in /boot/loader.conf on the root fs on the server, even if it is using grub later. This all assumes that your kernel is built with "options NFS_ROOT". If it built with "options BOOTP" etc, then it is an entirely different story. Good luck with it, rick ps: At some point, capturing the packets and looking at them in wireshark should tell you what it is doing and when. [stuff snipped for brevity] > Regards. > > > > > - > FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS > -- > View this message in context: > http://freebsd.1045724.n5.nabble.com/Some-NFS-server-V4-questions-tp5959433p5959595.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" > ___ 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"
Re: Some NFS server V4 questions
Beeblebrox wrote:
> 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?
>
Well, I thought that the root fs was remounted ("mount -u") using the
options specified in /etc/fstab for the root fs. As far as I know, putting
the "nolockd" option there should work.
rick
> >> 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"
___
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"
Re: Some NFS server V4 questions
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"
Re: Some NFS server V4 questions
On Sun, Oct 26, 2014 at 08:14:05AM -0400, Rick Macklem wrote: > Beeblebrox wrote: > > Sorry guys, we have a considerable time-zone difference. > > > > >> It appears that the sysctl must be set before mountd, nfsd are > > >> started to take effect. (Or they must be restarted after it is > > >> set.) > > I had apparently re-started nfsd but not mountd. This time > > re-starting both and launching the PXE client fails at mount_root > > stage as expected: > > exec /sbin/init: error 43 > > exec /rescue/init: error 43 > > panic: no init > > > > One cannot set "sysctl vfs.nfsd.server_min_nfsvers=4" until one of > > mountd/nfsd is started however, otherwise it gives an error. I have > > not tried, but I suppose this error does not happen when placeed in > > /etc/sysctl.conf? > > sysctl: unknown oid 'vfs.nfsd.server_min_nfsvers': No such file or > > directory > > > It works if it is /etc/sysctl.conf if "options NFSD" are specified > for the kernel, which is what GENERIC for i386 has. > > If "options NFSD" isn't in your kernel config, I think you'd have to > get nfsd.ko loaded before setting the sysctl and do both before > starting mountd. > > I don't know of a clean way to do this? > > Putting kldload and sysctl command lines in mountd_precmd() in > /etc/rc.d/mountd would do it I suspect. Maybe rc variables for > this should be added? (I haven't tried this since the only > kernels I have handy have "options NFSD" in them.) With the following patch, the same variables should work when set from the loader.conf (i.e. pre-boot) or using kenv(8). diff --git a/sys/fs/nfsserver/nfs_nfsdkrpc.c b/sys/fs/nfsserver/nfs_nfsdkrpc.c index d2145cc..4fb9c93 100644 --- a/sys/fs/nfsserver/nfs_nfsdkrpc.c +++ b/sys/fs/nfsserver/nfs_nfsdkrpc.c @@ -85,16 +85,16 @@ SYSCTL_DECL(_vfs_nfsd); SVCPOOL*nfsrvd_pool; static int nfs_privport = 0; -SYSCTL_INT(_vfs_nfsd, OID_AUTO, nfs_privport, CTLFLAG_RW, +SYSCTL_INT(_vfs_nfsd, OID_AUTO, nfs_privport, CTLFLAG_RWTUN, &nfs_privport, 0, "Only allow clients using a privileged port for NFSv2 and 3"); static int nfs_minvers = NFS_VER2; -SYSCTL_INT(_vfs_nfsd, OID_AUTO, server_min_nfsvers, CTLFLAG_RW, +SYSCTL_INT(_vfs_nfsd, OID_AUTO, server_min_nfsvers, CTLFLAG_RWTUN, &nfs_minvers, 0, "The lowest version of NFS handled by the server"); static int nfs_maxvers = NFS_VER4; -SYSCTL_INT(_vfs_nfsd, OID_AUTO, server_max_nfsvers, CTLFLAG_RW, +SYSCTL_INT(_vfs_nfsd, OID_AUTO, server_max_nfsvers, CTLFLAG_RWTUN, &nfs_maxvers, 0, "The highest version of NFS handled by the server"); static int nfs_proc(struct nfsrv_descript *, u_int32_t, SVCXPRT *xprt, ___ 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"
Re: Some NFS server V4 questions
Beeblebrox wrote: > Sorry guys, we have a considerable time-zone difference. > > >> It appears that the sysctl must be set before mountd, nfsd are > >> started to take effect. (Or they must be restarted after it is > >> set.) > I had apparently re-started nfsd but not mountd. This time > re-starting both and launching the PXE client fails at mount_root > stage as expected: > exec /sbin/init: error 43 > exec /rescue/init: error 43 > panic: no init > > One cannot set "sysctl vfs.nfsd.server_min_nfsvers=4" until one of > mountd/nfsd is started however, otherwise it gives an error. I have > not tried, but I suppose this error does not happen when placeed in > /etc/sysctl.conf? > sysctl: unknown oid 'vfs.nfsd.server_min_nfsvers': No such file or > directory > > >> Maybe it was the talk about getting rid of the oldnfs stuff that > >> made you think V2, 3 were going away? > Yes, that was it and I obviously misunderstood that thread. > > What's the max NFS version that supports mount_root from PXE clients > then? As I recall, this would be V3. However, root is consistently > being mounted as V2. > The fstab for diskless clients: > 192.168.2.1:/data/amd64 / nfs ro,nfsv30 0 > 192.168.2.1:/usr/local /usr/local nfs ro,nfsv40 0 > 192.168.2.1:/home /home nfs rw,nfsv4,hard,intr 0 0 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.) rick > > nfsstat shows "/" as NFSV2, while the other two are NFSV4. Changing > fstab entry to nfsv4 for root gives same result. > I tried set "sysctl vfs.nfsd.server_min_nfsvers=3" and I get the same > mount_root error as when this was set to 4. Im I missing something? > It does not seem that "vfs.nfsd.server_min_nfsvers" will be of much > use to me, unless I can get > V2 to mount as root. > > Regards. > > > > > - > FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS > -- > View this message in context: > http://freebsd.1045724.n5.nabble.com/Some-NFS-server-V4-questions-tp5959433p5959595.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" > ___ 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"
Re: Some NFS server V4 questions
Beeblebrox wrote: > Sorry guys, we have a considerable time-zone difference. > > >> It appears that the sysctl must be set before mountd, nfsd are > >> started to take effect. (Or they must be restarted after it is > >> set.) > I had apparently re-started nfsd but not mountd. This time > re-starting both and launching the PXE client fails at mount_root > stage as expected: > exec /sbin/init: error 43 > exec /rescue/init: error 43 > panic: no init > > One cannot set "sysctl vfs.nfsd.server_min_nfsvers=4" until one of > mountd/nfsd is started however, otherwise it gives an error. I have > not tried, but I suppose this error does not happen when placeed in > /etc/sysctl.conf? > sysctl: unknown oid 'vfs.nfsd.server_min_nfsvers': No such file or > directory > It works if it is /etc/sysctl.conf if "options NFSD" are specified for the kernel, which is what GENERIC for i386 has. If "options NFSD" isn't in your kernel config, I think you'd have to get nfsd.ko loaded before setting the sysctl and do both before starting mountd. I don't know of a clean way to do this? Putting kldload and sysctl command lines in mountd_precmd() in /etc/rc.d/mountd would do it I suspect. Maybe rc variables for this should be added? (I haven't tried this since the only kernels I have handy have "options NFSD" in them.) rick > >> Maybe it was the talk about getting rid of the oldnfs stuff that > >> made you think V2, 3 were going away? > Yes, that was it and I obviously misunderstood that thread. > > What's the max NFS version that supports mount_root from PXE clients > then? As I recall, this would be V3. However, root is consistently > being mounted as V2. > The fstab for diskless clients: > 192.168.2.1:/data/amd64 / nfs ro,nfsv30 0 > 192.168.2.1:/usr/local /usr/local nfs ro,nfsv40 0 > 192.168.2.1:/home /home nfs rw,nfsv4,hard,intr 0 0 > > nfsstat shows "/" as NFSV2, while the other two are NFSV4. Changing > fstab entry to nfsv4 for root gives same result. > I tried set "sysctl vfs.nfsd.server_min_nfsvers=3" and I get the same > mount_root error as when this was set to 4. Im I missing something? > It does not seem that "vfs.nfsd.server_min_nfsvers" will be of much > use to me, unless I can get > V2 to mount as root. > > Regards. > > > > > - > FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS > -- > View this message in context: > http://freebsd.1045724.n5.nabble.com/Some-NFS-server-V4-questions-tp5959433p5959595.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" > ___ 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"
Re: Some NFS server V4 questions
> On Oct 26, 2014, at 10:48 AM, Beeblebrox wrote: > > Sorry guys, we have a considerable time-zone difference. > >>> It appears that the sysctl must be set before mountd, nfsd are >>> started to take effect. (Or they must be restarted after it is set.) > I had apparently re-started nfsd but not mountd. This time re-starting both > and launching the PXE client fails at mount_root stage as expected: > exec /sbin/init: error 43 > exec /rescue/init: error 43 > panic: no init > > One cannot set "sysctl vfs.nfsd.server_min_nfsvers=4" until one of > mountd/nfsd is started however, otherwise it gives an error. I have not > tried, but I suppose this error does not happen when placeed in > /etc/sysctl.conf? > sysctl: unknown oid 'vfs.nfsd.server_min_nfsvers': No such file or directory > >>> Maybe it was the talk about getting rid of the oldnfs stuff that >>> made you think V2, 3 were going away? > Yes, that was it and I obviously misunderstood that thread. > > What's the max NFS version that supports mount_root from PXE clients then? As > I recall, this would be V3. However, root is consistently being mounted as V2. to get pxeboot to do v3, add: boot-nfsroot-options=“nfsv3” to /boot/loader.conf > The fstab for diskless clients: > 192.168.2.1:/data/amd64 / nfs ro,nfsv30 0 > 192.168.2.1:/usr/local /usr/local nfs ro,nfsv40 0 > 192.168.2.1:/home /home nfs rw,nfsv4,hard,intr 0 0 > > nfsstat shows "/" as NFSV2, while the other two are NFSV4. Changing fstab > entry to nfsv4 for root gives same result. > I tried set "sysctl vfs.nfsd.server_min_nfsvers=3" and I get the same > mount_root error as when this was set to 4. Im I missing something? It does > not seem that "vfs.nfsd.server_min_nfsvers" will be of much use to me, unless > I can get > V2 to mount as root. > > Regards. > > > > > - > FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS > -- > View this message in context: > http://freebsd.1045724.n5.nabble.com/Some-NFS-server-V4-questions-tp5959433p5959595.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" ___ 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"
Re: Some NFS server V4 questions
Sorry guys, we have a considerable time-zone difference. >> It appears that the sysctl must be set before mountd, nfsd are >> started to take effect. (Or they must be restarted after it is set.) I had apparently re-started nfsd but not mountd. This time re-starting both and launching the PXE client fails at mount_root stage as expected: exec /sbin/init: error 43 exec /rescue/init: error 43 panic: no init One cannot set "sysctl vfs.nfsd.server_min_nfsvers=4" until one of mountd/nfsd is started however, otherwise it gives an error. I have not tried, but I suppose this error does not happen when placeed in /etc/sysctl.conf? sysctl: unknown oid 'vfs.nfsd.server_min_nfsvers': No such file or directory >> Maybe it was the talk about getting rid of the oldnfs stuff that >> made you think V2, 3 were going away? Yes, that was it and I obviously misunderstood that thread. What's the max NFS version that supports mount_root from PXE clients then? As I recall, this would be V3. However, root is consistently being mounted as V2. The fstab for diskless clients: 192.168.2.1:/data/amd64 / nfs ro,nfsv30 0 192.168.2.1:/usr/local /usr/local nfs ro,nfsv40 0 192.168.2.1:/home /home nfs rw,nfsv4,hard,intr 0 0 nfsstat shows "/" as NFSV2, while the other two are NFSV4. Changing fstab entry to nfsv4 for root gives same result. I tried set "sysctl vfs.nfsd.server_min_nfsvers=3" and I get the same mount_root error as when this was set to 4. Im I missing something? It does not seem that "vfs.nfsd.server_min_nfsvers" will be of much use to me, unless I can get > V2 to mount as root. Regards. - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/Some-NFS-server-V4-questions-tp5959433p5959595.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"
Re: Some NFS server V4 questions
Russell L. Carter wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > > On 10/25/14 09:58, Beeblebrox wrote: > > Hi Russ, > > > >>> PXE client's /etc/fstab is: 92.168.2.1:/data/amd64 / nfs > >>> ro 0 0 192.168.2.1:/usr/local /usr/local nfs ro 0 > >> > >> Possibly need to arrange for mount_nfs to see -o nfsv4 (I use > >> mount_nfs -o nfsv4,minorversion=1) > > Yeah, that would work very likely and thanks. > > > > From a purist standpoint, what would be settings on server side to > > force NFSV4 offering only? This means, how can I configure NFS so > > that V2/V3 requests get denied AND logged for debug? > > > > I have vfs.nfsd.server_min_nfsvers=4 set on the server, and > when I mount_nfs -o nfsv3 on the client, the error the client > sees is > > [tcp] terp:/packages: NFSPROC_NULL: RPC: Program/version mismatch; > low > version = 4, high version = 4 > > Have to ^C to exit. > I just did a quick test. It appears that the sysctl must be set before mountd, nfsd are started to take effect. (Or they must be restarted after it is set.) rick > Nothing shows up in the server's log, but because of sloth I haven't > tried to make anything show up. Maybe there's an option. > > Best, > Russell > > -BEGIN PGP SIGNATURE- > Version: GnuPG v2 > > iQIcBAEBAgAGBQJUTAhKAAoJEFnLrGVSDFaEctoP/3VAFxrLfkYDPTsKrCMD0pJf > RrNY0ePTVueDltsVXeEpT/pxSzN7RKLhWL0AB0IsoTWBvZZCHTbwv7GvF0yufxNW > +oU29DEceIc8dxhXqjjOCKM3Na85C90idukemDG5ZaZoDU9d//POKaV1ET5HwQNq > mZ1q4pqNjnf/O0q+7KjOxVvOnA1g7T2x/HxvL7D0RbmO6EGoRNXbMzxidQmcRDSG > V4pmS5GoTUuOqTeXqYbrHJsF8tBaxKqcsOcz90LIWoilYCxiVccPY9SI+EYhX0hq > ExVzTvt5OvfNSmz252m8I+87Sw0KA9r06fTpbARuK9Afyt/KNcOU/vANjzDegzLG > 8u9TcnBfsqNR7K3pqyvt4jyVW6fliI79i1wpVw2ZNn02vGSn1l2iHWzddX9y0Hmj > l1VMM2nWgag8V7wHebRmxILZMHK+VU4gWxp4hTXm0GkXHV27vPWY7eMQtbz/e7yu > OpqPSUO7AEp6PTMCZoQY8uIEqmfJIKnyv2/ua3RgNtqM1srvjg1nugxXjfD8z9m6 > PH0EY691Rv5hUScXwRtcElO8pziKWFbiXE1HrpPDMnpTtq6Wg5r/ubwepWTrmNJC > FfdNOzTCVSF6nBMAo7pwV2P2ATHQkDQjMJJ7B8jZPOapCX59q2Cgth/jX0muiX3g > wKbO2ZvSZa7lDAmBcecj > =DKjs > -END PGP SIGNATURE- > ___ > 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" > ___ 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"
Re: Some NFS server V4 questions
Russell L. Carter wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > > On 10/25/14 09:58, Beeblebrox wrote: > > Hi Russ, > > > >>> PXE client's /etc/fstab is: 92.168.2.1:/data/amd64 / nfs > >>> ro 0 0 192.168.2.1:/usr/local /usr/local nfs ro 0 > >> > >> Possibly need to arrange for mount_nfs to see -o nfsv4 (I use > >> mount_nfs -o nfsv4,minorversion=1) > > Yeah, that would work very likely and thanks. > > > > From a purist standpoint, what would be settings on server side to > > force NFSV4 offering only? This means, how can I configure NFS so > > that V2/V3 requests get denied AND logged for debug? > > > > I have vfs.nfsd.server_min_nfsvers=4 set on the server, and > when I mount_nfs -o nfsv3 on the client, the error the client > sees is > > [tcp] terp:/packages: NFSPROC_NULL: RPC: Program/version mismatch; > low > version = 4, high version = 4 > > Have to ^C to exit. > > Nothing shows up in the server's log, but because of sloth I haven't > tried to make anything show up. Maybe there's an option. > There isn't an option to log the attempts, but it does seem to have disallowed NFSv3 RPCs. rick > Best, > Russell > > -BEGIN PGP SIGNATURE- > Version: GnuPG v2 > > iQIcBAEBAgAGBQJUTAhKAAoJEFnLrGVSDFaEctoP/3VAFxrLfkYDPTsKrCMD0pJf > RrNY0ePTVueDltsVXeEpT/pxSzN7RKLhWL0AB0IsoTWBvZZCHTbwv7GvF0yufxNW > +oU29DEceIc8dxhXqjjOCKM3Na85C90idukemDG5ZaZoDU9d//POKaV1ET5HwQNq > mZ1q4pqNjnf/O0q+7KjOxVvOnA1g7T2x/HxvL7D0RbmO6EGoRNXbMzxidQmcRDSG > V4pmS5GoTUuOqTeXqYbrHJsF8tBaxKqcsOcz90LIWoilYCxiVccPY9SI+EYhX0hq > ExVzTvt5OvfNSmz252m8I+87Sw0KA9r06fTpbARuK9Afyt/KNcOU/vANjzDegzLG > 8u9TcnBfsqNR7K3pqyvt4jyVW6fliI79i1wpVw2ZNn02vGSn1l2iHWzddX9y0Hmj > l1VMM2nWgag8V7wHebRmxILZMHK+VU4gWxp4hTXm0GkXHV27vPWY7eMQtbz/e7yu > OpqPSUO7AEp6PTMCZoQY8uIEqmfJIKnyv2/ua3RgNtqM1srvjg1nugxXjfD8z9m6 > PH0EY691Rv5hUScXwRtcElO8pziKWFbiXE1HrpPDMnpTtq6Wg5r/ubwepWTrmNJC > FfdNOzTCVSF6nBMAo7pwV2P2ATHQkDQjMJJ7B8jZPOapCX59q2Cgth/jX0muiX3g > wKbO2ZvSZa7lDAmBcecj > =DKjs > -END PGP SIGNATURE- > ___ > 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" > ___ 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"
Re: Some NFS server V4 questions
Russell L. Carter wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> On 10/25/14 03:07, Beeblebrox wrote:
> > * I can't get the NFS server to run V4 only. I have: sysctl
> > vfs.nfsd.server_min_nfsvers=4
> >
>
> [...]
>
> > PXE client's /etc/fstab is: 92.168.2.1:/data/amd64 / nfs
> > ro 0 0 192.168.2.1:/usr/local /usr/local nfs ro 0
> > 0 192.168.2.1:/home /home nfs rw,hard,intr0 0
> >
>
> Possibly need to arrange for mount_nfs to see -o nfsv4
> (I use mount_nfs -o nfsv4,minorversion=1)
>
> Then nfsstat shows eg:
>
> terp:/library on /mnt/terp/library
> nfsv4,minorversion=1,tcp,resvport,hard,cto,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=65536,wsize=65536,readdirsize=65536,readahead=1,wcommitsize=2798255,timeout=120,retrans=2147483647
>
> HTH,
> Russell
>
> > * Considering V2/V3 for NFS is getting dropped from code base, PXE
> > clients used to need max V3 as root and could not mount_root with
> > V4. Has this changed? If so, what services do the clients need to
> > get V4 on root working (RO, no RW)?
>
As noted in the other reply, I am not aware of any plan to get rid
of NFSv2 or v3 and would oppose any such plan.
rick
> > * There was a simple command to show from server-side what version
> > of NFS the exports were running, but I seem to have lost that. Any
> > clues?
> >
> > * Have any of these services become capable of running from inside
> > a jail environment? {rpcbind mountd nfsd nfsuserd} - it does not
> > seem so, but just checking.
> >
> > Thanks and Regards.
> >
> >
> >
> > - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this
> > message in context:
> > http://freebsd.1045724.n5.nabble.com/Some-NFS-server-V4-questions-tp5959433.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"
> >
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iQIcBAEBAgAGBQJUS8a3AAoJEFnLrGVSDFaEvWEP/iIKgw1kTmGQqgYAzVY++8uq
> X3XMSnUFNGkyZSO/cz9gCO8S+oXkWVD8z3UbTKtyPCdTHhp48klTRW+ceSGvfhq2
> oyWfcM5bXbOBLQZaoz66IL77mZHlWOTOLoGyNQZp7x/7KXETN7nK+qxQ1WDD7WM9
> BW8fC+krQ4F5Tvqc70fylu93QKKUiqi26cOMWuRLTwgLXJY+NtPLMjH+SadDonNC
> FvszjFpTsoP7cKPWA0vPA2iLb3Q43DT1+k23r6iY33JzTX2LW+zpzk+i4wEneNE8
> JAgGqsFB08sH8krBrKo3n5+zcd5R0mZu3uX9a0CQJYiNHg6Phh4QgyETTYJT0ig/
> mF1Q7V5z4FHLKdZigqO2WjNN2l2zfzDlUWfDTyc/b8CZIaPJemdqADsBVl76UdX8
> 2HspYZdAxR2zPc9EmpNPQJAksBFyUpwZy6cpHW+7wrkeeYoTWZLYV5sm4IscOzEE
> tdof9VRIT+DGPrxLPFxO8tQiOV0eQWh3Om7Tlp92b3no9A3aUObQGIltvEEYQDKt
> CobSmiLRSx0FK/pGYrYZilJlWStJLHySvnpbEkVDJGVL9Ua42Jn/VMXfBksRz01P
> 53wFmW7RAj8yyzDKA8P7rTjoJdypBRJZXphk+svceGOKv8Bxrcx3xgyF82Cl8YPk
> Kl2YChCpbLewc+zxmRCz
> =ShKh
> -END PGP SIGNATURE-
> ___
> 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"
>
___
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"
Re: Some NFS server V4 questions
Beeblebrox wrote:
> * I can't get the NFS server to run V4 only. I have:
> sysctl vfs.nfsd.server_min_nfsvers=4
>
Hmm. With this set the NFS server shouldn't accept V2, 3
RPCs. The mount will work, since that is done by the Mount
protocol (mountd), but the client should be saying "server
not responding..." whenever it tries to access the V2, 3
mounts. Not sure why NFSv3 is still working after this is set.
I'll try a quick test of it here.
> I start all NFS-related services manually (from script)
> #!/bin/sh
> rpcbind -s -h 192.168.2.1
> mountd -rnl -h 192.168.2.1
> nfsd -ut -n 4 -h 192.168.2.1
> nfsuserd
>
> /etc/exports has:
> V4: / -network 192.168.2.0/26
> /data/amd64 /data/amd64/boot/s386-ro -network 192.168.2.0/26
> /usr/local-ro -maproot=0 -network 192.168.2.0/26
> /home -network 192.168.2.0/26
>
> Running "nfsstat -m" from a PXE client gives me:
> 192.168.2.1:/data/amd64 on /
> nfsv2,tcp,resvport,hard,cto,lockd,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=8192,wsize=8192,readdirsize=8192,readahead=1,wcommitsize=1997092,timeout=120,retrans=2
> 192.168.2.1:/home on /home
> nfsv3,tcp,resvport,hard,intr,cto,lockd,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=65536,wsize=65536,readdirsize=65536,readahead=1,wcommitsize=1997092,timeout=120,retrans=2
> 192.168.2.1:/usr/local on /usr/local
> nfsv3,tcp,resvport,hard,cto,lockd,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=65536,wsize=65536,readdirsize=65536,readahead=1,wcommitsize=1997092,timeout=120,retrans=2
>
> The PXE-booted kernel is compiled with: nfscommon, nfssvc, nfs,
> nfscl,
> nfslock
> On server side, in addition to the above, these are loaded as
> modules:
> acl_nfs4.ko, nfsd.ko, nfslockd.ko
>
> PXE client's /etc/rc.conf the only NFS-related entry is:
> nfs_client_enable="YES"
>
> PXE client's /etc/fstab is:
> 92.168.2.1:/data/amd64 / nfs ro 0 0
> 192.168.2.1:/usr/local /usr/local nfs ro 0 0
> 192.168.2.1:/home /home nfs rw,hard,intr0 0
>
>
> * Considering V2/V3 for NFS is getting dropped from code base, PXE
> clients
> used to need max V3 as root and could not mount_root with V4. Has
> this
> changed? If so, what services do the clients need to get V4 on root
> working
> (RO, no RW)?
>
I am not aware of any plans to drop V2/V3. Although V2 isn't used much
any more V3 will be around for a long time to come, imho. (I'll probably
be long gone before V3 is.)
The new client and server support V2, 3 and 4. (Maybe it was the talk
about getting rid of the oldnfs stuff that made you think V2, 3 were
going away?
rick
> * There was a simple command to show from server-side what version of
> NFS
> the exports were running, but I seem to have lost that. Any clues?
>
> * Have any of these services become capable of running from inside a
> jail
> environment? {rpcbind mountd nfsd nfsuserd} - it does not seem so,
> but just
> checking.
>
> Thanks and Regards.
>
>
>
> -
> FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
> --
> View this message in context:
> http://freebsd.1045724.n5.nabble.com/Some-NFS-server-V4-questions-tp5959433.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"
>
___
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"
Re: Some NFS server V4 questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/25/14 09:58, Beeblebrox wrote: > Hi Russ, > >>> PXE client's /etc/fstab is: 92.168.2.1:/data/amd64 / nfs >>> ro 0 0 192.168.2.1:/usr/local /usr/local nfs ro 0 >> >> Possibly need to arrange for mount_nfs to see -o nfsv4 (I use >> mount_nfs -o nfsv4,minorversion=1) > Yeah, that would work very likely and thanks. > > From a purist standpoint, what would be settings on server side to > force NFSV4 offering only? This means, how can I configure NFS so > that V2/V3 requests get denied AND logged for debug? > I have vfs.nfsd.server_min_nfsvers=4 set on the server, and when I mount_nfs -o nfsv3 on the client, the error the client sees is [tcp] terp:/packages: NFSPROC_NULL: RPC: Program/version mismatch; low version = 4, high version = 4 Have to ^C to exit. Nothing shows up in the server's log, but because of sloth I haven't tried to make anything show up. Maybe there's an option. Best, Russell -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJUTAhKAAoJEFnLrGVSDFaEctoP/3VAFxrLfkYDPTsKrCMD0pJf RrNY0ePTVueDltsVXeEpT/pxSzN7RKLhWL0AB0IsoTWBvZZCHTbwv7GvF0yufxNW +oU29DEceIc8dxhXqjjOCKM3Na85C90idukemDG5ZaZoDU9d//POKaV1ET5HwQNq mZ1q4pqNjnf/O0q+7KjOxVvOnA1g7T2x/HxvL7D0RbmO6EGoRNXbMzxidQmcRDSG V4pmS5GoTUuOqTeXqYbrHJsF8tBaxKqcsOcz90LIWoilYCxiVccPY9SI+EYhX0hq ExVzTvt5OvfNSmz252m8I+87Sw0KA9r06fTpbARuK9Afyt/KNcOU/vANjzDegzLG 8u9TcnBfsqNR7K3pqyvt4jyVW6fliI79i1wpVw2ZNn02vGSn1l2iHWzddX9y0Hmj l1VMM2nWgag8V7wHebRmxILZMHK+VU4gWxp4hTXm0GkXHV27vPWY7eMQtbz/e7yu OpqPSUO7AEp6PTMCZoQY8uIEqmfJIKnyv2/ua3RgNtqM1srvjg1nugxXjfD8z9m6 PH0EY691Rv5hUScXwRtcElO8pziKWFbiXE1HrpPDMnpTtq6Wg5r/ubwepWTrmNJC FfdNOzTCVSF6nBMAo7pwV2P2ATHQkDQjMJJ7B8jZPOapCX59q2Cgth/jX0muiX3g wKbO2ZvSZa7lDAmBcecj =DKjs -END PGP SIGNATURE- ___ 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"
Re: Some NFS server V4 questions
Hi Russ, > > PXE client's /etc/fstab is: 92.168.2.1:/data/amd64 / nfs > > ro 0 0 192.168.2.1:/usr/local /usr/local nfs ro 0 > > Possibly need to arrange for mount_nfs to see -o nfsv4 > (I use mount_nfs -o nfsv4,minorversion=1) Yeah, that would work very likely and thanks. >From a purist standpoint, what would be settings on server side to force NFSV4 >offering only? This means, how can I configure NFS so that V2/V3 requests get >denied AND logged for debug? - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/Some-NFS-server-V4-questions-tp5959433p5959475.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"
Re: Some NFS server V4 questions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/25/14 03:07, Beeblebrox wrote:
> * I can't get the NFS server to run V4 only. I have: sysctl
> vfs.nfsd.server_min_nfsvers=4
>
[...]
> PXE client's /etc/fstab is: 92.168.2.1:/data/amd64 / nfs
> ro 0 0 192.168.2.1:/usr/local /usr/local nfs ro 0
> 0 192.168.2.1:/home /home nfs rw,hard,intr0 0
>
Possibly need to arrange for mount_nfs to see -o nfsv4
(I use mount_nfs -o nfsv4,minorversion=1)
Then nfsstat shows eg:
terp:/library on /mnt/terp/library
nfsv4,minorversion=1,tcp,resvport,hard,cto,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=65536,wsize=65536,readdirsize=65536,readahead=1,wcommitsize=2798255,timeout=120,retrans=2147483647
HTH,
Russell
> * Considering V2/V3 for NFS is getting dropped from code base, PXE
> clients used to need max V3 as root and could not mount_root with
> V4. Has this changed? If so, what services do the clients need to
> get V4 on root working (RO, no RW)?
> * There was a simple command to show from server-side what version
> of NFS the exports were running, but I seem to have lost that. Any
> clues?
>
> * Have any of these services become capable of running from inside
> a jail environment? {rpcbind mountd nfsd nfsuserd} - it does not
> seem so, but just checking.
>
> Thanks and Regards.
>
>
>
> - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this
> message in context:
> http://freebsd.1045724.n5.nabble.com/Some-NFS-server-V4-questions-tp5959433.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"
>
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBAgAGBQJUS8a3AAoJEFnLrGVSDFaEvWEP/iIKgw1kTmGQqgYAzVY++8uq
X3XMSnUFNGkyZSO/cz9gCO8S+oXkWVD8z3UbTKtyPCdTHhp48klTRW+ceSGvfhq2
oyWfcM5bXbOBLQZaoz66IL77mZHlWOTOLoGyNQZp7x/7KXETN7nK+qxQ1WDD7WM9
BW8fC+krQ4F5Tvqc70fylu93QKKUiqi26cOMWuRLTwgLXJY+NtPLMjH+SadDonNC
FvszjFpTsoP7cKPWA0vPA2iLb3Q43DT1+k23r6iY33JzTX2LW+zpzk+i4wEneNE8
JAgGqsFB08sH8krBrKo3n5+zcd5R0mZu3uX9a0CQJYiNHg6Phh4QgyETTYJT0ig/
mF1Q7V5z4FHLKdZigqO2WjNN2l2zfzDlUWfDTyc/b8CZIaPJemdqADsBVl76UdX8
2HspYZdAxR2zPc9EmpNPQJAksBFyUpwZy6cpHW+7wrkeeYoTWZLYV5sm4IscOzEE
tdof9VRIT+DGPrxLPFxO8tQiOV0eQWh3Om7Tlp92b3no9A3aUObQGIltvEEYQDKt
CobSmiLRSx0FK/pGYrYZilJlWStJLHySvnpbEkVDJGVL9Ua42Jn/VMXfBksRz01P
53wFmW7RAj8yyzDKA8P7rTjoJdypBRJZXphk+svceGOKv8Bxrcx3xgyF82Cl8YPk
Kl2YChCpbLewc+zxmRCz
=ShKh
-END PGP SIGNATURE-
___
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"
Some NFS server V4 questions
* I can't get the NFS server to run V4 only. I have:
sysctl vfs.nfsd.server_min_nfsvers=4
I start all NFS-related services manually (from script)
#!/bin/sh
rpcbind -s -h 192.168.2.1
mountd -rnl -h 192.168.2.1
nfsd -ut -n 4 -h 192.168.2.1
nfsuserd
/etc/exports has:
V4: / -network 192.168.2.0/26
/data/amd64 /data/amd64/boot/s386-ro -network 192.168.2.0/26
/usr/local -ro -maproot=0 -network 192.168.2.0/26
/home -network 192.168.2.0/26
Running "nfsstat -m" from a PXE client gives me:
192.168.2.1:/data/amd64 on /
nfsv2,tcp,resvport,hard,cto,lockd,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=8192,wsize=8192,readdirsize=8192,readahead=1,wcommitsize=1997092,timeout=120,retrans=2
192.168.2.1:/home on /home
nfsv3,tcp,resvport,hard,intr,cto,lockd,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=65536,wsize=65536,readdirsize=65536,readahead=1,wcommitsize=1997092,timeout=120,retrans=2
192.168.2.1:/usr/local on /usr/local
nfsv3,tcp,resvport,hard,cto,lockd,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=65536,wsize=65536,readdirsize=65536,readahead=1,wcommitsize=1997092,timeout=120,retrans=2
The PXE-booted kernel is compiled with: nfscommon, nfssvc, nfs, nfscl,
nfslock
On server side, in addition to the above, these are loaded as modules:
acl_nfs4.ko, nfsd.ko, nfslockd.ko
PXE client's /etc/rc.conf the only NFS-related entry is:
nfs_client_enable="YES"
PXE client's /etc/fstab is:
92.168.2.1:/data/amd64 / nfs ro 0 0
192.168.2.1:/usr/local /usr/local nfs ro 0 0
192.168.2.1:/home /home nfs rw,hard,intr0 0
* Considering V2/V3 for NFS is getting dropped from code base, PXE clients
used to need max V3 as root and could not mount_root with V4. Has this
changed? If so, what services do the clients need to get V4 on root working
(RO, no RW)?
* There was a simple command to show from server-side what version of NFS
the exports were running, but I seem to have lost that. Any clues?
* Have any of these services become capable of running from inside a jail
environment? {rpcbind mountd nfsd nfsuserd} - it does not seem so, but just
checking.
Thanks and Regards.
-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Some-NFS-server-V4-questions-tp5959433.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"
