NFS Changes On Linux 5.3 Will Allow Clients To Use New "nconnect" Mount Option

[S.Pam]

Adding the Linux boxes to your AD domain cures that problem quickly and easily. Don't like AD? FreeIPA is an answer as well.

That's my point. Most home users, even though they might be Linux users, would not have an AD domain. Besides, isn't Samba the only alternative to an AD domain unless you use Windows server? Can the FreeIPA replace that? Never heard of it.

Can I even use SMB for homedirectory on linux ?

I don't see why not? Samba and the CIFS kernel modules supports native UNIX acls and stuff like that.

[torsionbar28]

Is anyone still actually using NFS?

NFS is a very mature and reliable protocol, and v4 introduces some awesome feature enhancements over previous versions. We use NFS v4 extensively between RHEL VM's and a few HP-UX servers at work, in a fairly large environment spanning multiple datacenters. It works really well. I also use NFSv4 at home, for mounting file shares from my server in the basement, to various pc's throughout the house. Works very well there too. Quite frankly, I'm not sure why anyone would not want to use NFS, unless they're stuck using some old proprietary non-unix OS. With 10 Gbit+ Ethernet speeds nowadays, NFS is an especially attractive solution for an increasing array of use cases. There are even major database vendors now who support running on NFS, something that was unimaginable a few years ago.

[torsionbar28]

That's my point. Most home users, even though they might be Linux users, would not have an AD domain. Besides, isn't Samba the only alternative to an AD domain unless you use Windows server? Can the FreeIPA replace that? Never heard of it.

FreeIPA aka Red Hat Identity Management is a robust domain architecture. We use it on ~200 RHEL VM's here at work. It supports multi-master domain controllers and fully customizable topology. Development of FreeIPA has really picked up steam in recent years, and I'd consider it an enterprise grade solution.

[S.Pam]

How is that helping the normal home user?

[Nairn]

Is anyone still actually using NFS?

Yes, I am; I'm streaming HD video from one Raspberry Pi to another, although they're are being replaced this week with Orange Pi 3s.

[deant]

I have a small company with mosty linux machines and some windows ones. The main file server serves files trough OpenVPN to the linux machines via NFS and to the windows ones via SMB. Why is that? SMB is totaly unsuported and hard to mount under GUIs like gnome/mate/cinnamon. SMB and NFS actualy work quite well and sometimes i forget that i use both!

[S.Pam]

Has anyone done any bechmarks regarding nconnect=X ? I just tested with kernel-5.3.0 just out and I see nowhere if the option is enabled or not. mount does not complain, but also does not show the option.

mount output:

192.168.0.1:/usr/portage on /usr/portage type nfs4 (rw,noatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.0.50,local_lock=none,addr=192.168.0.1)

fstab is this:

192.168.0.1:/usr/portage        /usr/portage/           nfs     nconnect=2,soft,noatime,rw,tcp,vers=4.2,ac,async,nofail 0 0

Might aswell include mountstats:

# mountstats /usr/portage/
Stats for 192.168.0.1:/usr/portage mounted on /usr/portage:

  NFS mount options: rw,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,acregmin=3,acregmax=60,acdirmin=30,acdirmax=60,soft,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.0.50,local_lock=none
  NFS server capabilities: caps=0x7fbffff,wtmult=512,dtsize=32768,bsize=0,namlen=255
  NFSv4 capability flags: bm0=0xfdffbfff,bm1=0x40f9be3e,bm2=0x28803,acl=0x3,sessions,pnfs=notconfigured,lease_time=90,lease_expired=0
  NFS security flavor: 1  pseudoflavor: 0

NFS byte counts:
  applications read 72825547 bytes via read(2)
  applications wrote 0 bytes via write(2)
  applications read 0 bytes via O_DIRECT read(2)
  applications wrote 0 bytes via O_DIRECT write(2)
  client read 68250802 bytes via NFS READ
  client wrote 0 bytes via NFS WRITE
RPC statistics:
  153547 RPC requests sent, 153547 RPC replies received (0 XIDs not found)
  average backlog queue length: 0

CLOSE:
        38653 ops (25%)
        avg bytes sent per op: 204      avg bytes received per op: 123
        backlog wait: 0.017023  RTT: 0.423098   total execute time: 0.456963 (milliseconds)
READ:
        37510 ops (24%)
        avg bytes sent per op: 209      avg bytes received per op: 1925
        backlog wait: 0.016422  RTT: 0.607145   total execute time: 0.643082 (milliseconds)
OPEN_NOATTR:
        31985 ops (20%)
        avg bytes sent per op: 262      avg bytes received per op: 345
        backlog wait: 0.017102  RTT: 0.491105   total execute time: 0.525684 (milliseconds)
DELEGRETURN:
        31767 ops (20%)
        avg bytes sent per op: 214      avg bytes received per op: 160
        backlog wait: 1002.817263       RTT: 2.328706   total execute time: 1005.167249 (milliseconds)
OPEN:
        6707 ops (4%)   39 errors (0%)
        avg bytes sent per op: 288      avg bytes received per op: 404
        backlog wait: 0.015953  RTT: 0.490681   total execute time: 0.523930 (milliseconds)
LOOKUP:
        3241 ops (2%)   258 errors (7%)
        avg bytes sent per op: 253      avg bytes received per op: 291
        backlog wait: 0.002468  RTT: 0.514039   total execute time: 0.536254 (milliseconds)
ACCESS:
        2500 ops (1%)
        avg bytes sent per op: 233      avg bytes received per op: 167
        backlog wait: 0.002800  RTT: 0.511600   total execute time: 0.534000 (milliseconds)
READDIR:
        787 ops (0%)
        avg bytes sent per op: 230      avg bytes received per op: 20402
        backlog wait: 0.002541  RTT: 2.266836   total execute time: 2.303685 (milliseconds)
GETATTR:
        269 ops (0%)
        avg bytes sent per op: 223      avg bytes received per op: 240
        backlog wait: 0.000000  RTT: 0.542751   total execute time: 0.568773 (milliseconds)
SEQUENCE:
        12 ops (0%)
        avg bytes sent per op: 116      avg bytes received per op: 80
        backlog wait: 0.000000  RTT: 0.583333   total execute time: 0.666667 (milliseconds)
STATFS:
        2 ops (0%)
        avg bytes sent per op: 208      avg bytes received per op: 160
        backlog wait: 0.000000  RTT: 0.000000   total execute time: 0.000000 (milliseconds)
SERVER_CAPS:
        2 ops (0%)
        avg bytes sent per op: 172      avg bytes received per op: 164
        backlog wait: 0.000000  RTT: 0.000000   total execute time: 0.000000 (milliseconds)
EXCHANGE_ID:
        2 ops (0%)
        avg bytes sent per op: 232      avg bytes received per op: 92
        backlog wait: 0.000000  RTT: 0.000000   total execute time: 0.500000 (milliseconds)
NULL:
        1 ops (0%)
        avg bytes sent per op: 44       avg bytes received per op: 24
        backlog wait: 0.000000  RTT: 0.000000   total execute time: 1.000000 (milliseconds)
FSINFO:
        1 ops (0%)
        avg bytes sent per op: 172      avg bytes received per op: 164
        backlog wait: 0.000000  RTT: 0.000000   total execute time: 0.000000 (milliseconds)
PATHCONF:
        1 ops (0%)
        avg bytes sent per op: 164      avg bytes received per op: 116
        backlog wait: 0.000000  RTT: 0.000000   total execute time: 0.000000 (milliseconds)
CREATE_SESSION:
        1 ops (0%)
        avg bytes sent per op: 192      avg bytes received per op: 124
        backlog wait: 0.000000  RTT: 0.000000   total execute time: 0.000000 (milliseconds)
RECLAIM_COMPLETE:
        1 ops (0%)
        avg bytes sent per op: 124      avg bytes received per op: 88
        backlog wait: 0.000000  RTT: 6.000000   total execute time: 6.000000 (milliseconds)