The only thing that can be an issue with NFS is that it's prone to hard locks from time to time. This is of course infrastructure-dependent, but everyone should know this happens and how to deal with it. I'd also like to add that NFS shares has a cache with a update timer attached to it so any updates to a shared directory aren't necessarily listed in the shared dir unless your explicitly force a cache update or let the update timer run out so it automagically updates the listing itself. Small things that matters.
yeah this is strange issue i ran into with default windows explorer. After copying a folder full of files, and try again, the explorer doesn't seem to "recognize" the files in the folder , and just proceed to copy again. But SMB overhead is so bad it's unusable for application, and I really don't want to iscsi since I just abandoned NTFS in favor of ZFS. : ( ; I assume the cache timer you mentioned is the cause of the issue i am observing? If so do you have any way to mitigate that?
recently found an article titled "Mounting NFS Shares in Windows Using Identity Mapping", it describe how to setup uid and gid for a windows user. This way, nfs shearing can be mounted only for seted-up user instead of any user can mount the nfs share. A bit more control I would say. Perhaps it can be implemented to windows-tool-box in someway.
One big pluss for sharing over NFS instead of SMB is when you have large picture collections/folders on your share and you want to list them on thumbnails view. Thumbnails generation is just insanely faster in my experience.
Great video👍 A lot of good color commentary aground puts and takes NFS vs SMB: speed, access control, etc. The SAN diagramming was great; pls show explanatory drawings more often.
New-PSDrive -name "N" -PSProvider FileSystem -Root "\\server\share" -Persist is the way to mount a samba share in Windows that persists on reboot. Set-NFSShare is something you would do on the server to make the share available to other computers In Powershell, "mount" is an alias for New-PSDrive, you need to specify mount.exe
One major issue with provided Windows NFS client is lack of UTF-8 support, this means destroying file names containing characters that are not ascii or a few Asian charsets. A working alternative is Dokan / Dokany2 with fuse-nfs -- or WinFsp with nfs-win but for me is so slow it is unusable.
New channel for more streaming/other stuff. He still has the Christ Titus Tech channel. Creators benefit from multiple channels for different types of content because YT algorithms. . . .
No, to be fair, that isnt how 'Big' business is setup. That is really small/mid size shop setup stuff... Anything BIG requiring performance isnt touching iSCSI or NFS, or SMB for that matter Your SAN presentation is multi-fabric fibre for storage presentation. LACP connections are reserved for the Ethernet layer - application data transfer, not storage. None of that is cheap of course, hence its in the land of big business. SAN arrays north of 100million with multiple 100GB fibre links for cross site replication to your remote datacenters. The struggle is trying to explain to the customer in such an enterprise setup that the video that they saw on youtube espousing NFS as the speedy connection to be had between their mixed OS fleet is the way to go may not actually have any sane bearing on the pond in which their kit is swimming... That their data lake has more IOs when its at its quietest than any NFS setup is ever going to sanely look at, let along have any chance of dealing with. Bless their cotton socks.
All of this back and forth wrestling with the command line errors when you can just right click in "This PC" folder, and select "Add a network location" to do exactly the same from the GUI. I get that there are some situations where the command line could be useful, like automating the process for many computers in a network. But in this case it seems that the shell is just getting in the way of getting the job done for no apparent reason.
Try that again for a kerberos enabled (-o sec=krb5p) NFS share, let me know how many mouse clicks it takes you before you give up realizing that it will never achieve it... ;-)
The only thing that can be an issue with NFS is that it's prone to hard locks from time to time. This is of course infrastructure-dependent, but everyone should know this happens and how to deal with it.
I'd also like to add that NFS shares has a cache with a update timer attached to it so any updates to a shared directory aren't necessarily listed in the shared dir unless your explicitly force a cache update or let the update timer run out so it automagically updates the listing itself.
Small things that matters.
yeah this is strange issue i ran into with default windows explorer. After copying a folder full of files, and try again, the explorer doesn't seem to "recognize" the files in the folder , and just proceed to copy again. But SMB overhead is so bad it's unusable for application, and I really don't want to iscsi since I just abandoned NTFS in favor of ZFS. : ( ; I assume the cache timer you mentioned is the cause of the issue i am observing? If so do you have any way to mitigate that?
Is this still true for NFSv4?
I've improved my life and that of Mrs Martin by completely dumping Windows and switching to Ubuntu.
recently found an article titled "Mounting NFS Shares in Windows Using Identity Mapping", it describe how to setup uid and gid for a windows user. This way, nfs shearing can be mounted only for seted-up user instead of any user can mount the nfs share. A bit more control I would say. Perhaps it can be implemented to windows-tool-box in someway.
One big pluss for sharing over NFS instead of SMB is when you have large picture collections/folders on your share and you want to list them on thumbnails view. Thumbnails generation is just insanely faster in my experience.
Great video👍
A lot of good color commentary aground puts and takes NFS vs SMB: speed, access control, etc.
The SAN diagramming was great; pls show explanatory drawings more often.
New-PSDrive -name "N" -PSProvider FileSystem -Root "\\server\share" -Persist is the way to mount a samba share in Windows that persists on reboot.
Set-NFSShare is something you would do on the server to make the share available to other computers
In Powershell, "mount" is an alias for New-PSDrive, you need to specify mount.exe
One major issue with provided Windows NFS client is lack of UTF-8 support, this means destroying file names containing characters that are not ascii or a few Asian charsets. A working alternative is Dokan / Dokany2 with fuse-nfs -- or WinFsp with nfs-win but for me is so slow it is unusable.
Hey, this isn't a Need for Speed video...
You can also have PowerShell run an explicit command shell command via the "cmd /c {some cmd string}"
Chris is this a ‘new’ channel or a renamed ‘Chris Titus Tech’ channel?
New channel for more streaming/other stuff. He still has the Christ Titus Tech channel. Creators benefit from multiple channels for different types of content because YT algorithms. . . .
I'd like to try newtek codec NDI
Smb is my preference
I wish it was just a one hit button for your tool.
No, to be fair, that isnt how 'Big' business is setup. That is really small/mid size shop setup stuff...
Anything BIG requiring performance isnt touching iSCSI or NFS, or SMB for that matter
Your SAN presentation is multi-fabric fibre for storage presentation. LACP connections are reserved for the Ethernet layer - application data transfer, not storage.
None of that is cheap of course, hence its in the land of big business. SAN arrays north of 100million with multiple 100GB fibre links for cross site replication to your remote datacenters.
The struggle is trying to explain to the customer in such an enterprise setup that the video that they saw on youtube espousing NFS as the speedy connection to be had between their mixed OS fleet is the way to go may not actually have any sane bearing on the pond in which their kit is swimming... That their data lake has more IOs when its at its quietest than any NFS setup is ever going to sanely look at, let along have any chance of dealing with. Bless their cotton socks.
Switchers or just switches
No File Security
All of this back and forth wrestling with the command line errors when you can just right click in "This PC" folder, and select "Add a network location" to do exactly the same from the GUI.
I get that there are some situations where the command line could be useful, like automating the process for many computers in a network. But in this case it seems that the shell is just getting in the way of getting the job done for no apparent reason.
Try that again for a kerberos enabled (-o sec=krb5p) NFS share, let me know how many mouse clicks it takes you before you give up realizing that it will never achieve it... ;-)
-Persist
seems simple
net use Z: \\ip\path\to /persistent:yes
Easiest way to make it persistent w/o any bat files.