On 07/07/2020 01:52 AM, Roger Oberholtzer wrote:
Why NFS? Mainly because it is easy to share and unshare directories independently. The server maintains a disk array with 24 removable disks (hot swappable). These disks come and go independently. So they need to be exported and unexported independently. I do not see how to do this with SAMBA. All is in one big file and they are shared and unshared together. We do not want to disrupt some disks while changing others. So NFS seemed a way to go. If I have missed something in SAMBA, I would be ever so happy. That was question two.
There are pluses and minuses for NFS usage. About 15+ years ago, I went to straight smb and samba for Windows Linux filesystem interoperability. Somewhere around Samba 2.02a on either SuSE 7 or 8 pro. I made the switch and never looked back. Samba still has a "standalone" file-server mode which is what I use (but it has grown way beyond simply file server/filesystem access control to a full blown domain controller (I just don't have a need for that enterprise level interoperability or complexity. The good news is as a file server and SMB application, configuration with the good-ole smb.conf is all that is still required. If your windows NFS connections are flaky, just CIFS mount the windows shares as part of the Linux side of your cluster and just work with them as if they were Linux.It's not that bad to get on top of. It works for so long without having to mess with it -- I end up having to re-learn (or at least refresh on it) any of the very rare times I need to make changes. That's a good measure of a setup. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org