Look Im not saying NFS doesn’t have a time and a place as it does but this idea that Linux machines should only talk NFS and somehow that SMB is purely for legacy Windows systems is a very old fashioned and outdated view.
SMB is a great choice for mixed OS access, AD environments, General purpose file shares to name a few.
NFS is great for Linux servers, Datastores, VM storage to name a few.
We’re talking about an environment with a TrueNAS server (Linux), and a Kubuntu (Linux) client. There’s no mention of other OSes, and it’s obviously not an AD environment.
Exactly what advantage does SMB have here? It has a huge performance penalty compared to NFS and doesn’t support Unix permissions.
My advice for the average user regardless of their client OS would be to use SMB if you are using your TrueNAS as a general purpose file share. It is much more flexible going forward should people join your network and you wish to share data and allows greater and more granular permissions using NFSv4 ACLs. It also provides better security by default because it relies on user based authentication rather than IP based auth.
I do not agree with this statement. Once again the average home user accessing either over WiFi or 1Gb is not going to see any difference in performance. If anything NFS could be worse if the client is requesting sync writes.
Not sure why you are getting hung-up about this? It’s not a failure it’s by design to improve permissions.
I am using SMB cause that is what I always used in the past with a mix of Windows and Linux.
I created a NFS share on TrueNAS
I tried to mount it on my Kubuntu laptop, I think it does..
Then I try to access the folder and it only asks for a password…. Which anything I type in fails and locks it out.