User Tools

Site Tools


tcpip_nfs_-_how_large_of_a_file_can_my_nfs_server_or_client_handle

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
tcpip_nfs_-_how_large_of_a_file_can_my_nfs_server_or_client_handle [2019/02/08 23:40] mmacgregortcpip_nfs_-_how_large_of_a_file_can_my_nfs_server_or_client_handle [2019/02/11 19:48] mmacgregor
Line 8: Line 8:
 ===== Details ===== ===== Details =====
  
-The answer depends on which IP stack you are running on your OpenVMS machine and which version of Network File System (NFS) is installed.  2 gigabytes was a major power of 2 boundary for almost all of the IP stacks.  NFS v2 had that limitation.  NFS v3 allowed files to exceed 2 GB and typically that meant it is now capable of up to 4 GB in size.  However, each vendor implemented this in different ways (ie, perhaps Server only and not the Client).  So here is the information that we've been able to track down for each vendor.+The answer depends on which IP stack you are running on your OpenVMS machine and which version of Network File System (NFS) is installed.  2 gigabytes was a major power of 2 boundary for almost all of the IP stacks.  NFS v2 had that limitation because it only used 32 bits.  Since one of the bits was signed, that means 2^31 power or 2,147,483,648 bytes.  NFS v3 allowed files to exceed 2 GB because it utilized 64 bits of space.  However, each vendor implemented this in different ways (ie, perhaps Server only and not the Client).  So here is the information that we've been able to track down for each vendor.
  
 **TCPware:** **TCPware:**
tcpip_nfs_-_how_large_of_a_file_can_my_nfs_server_or_client_handle.txt · Last modified: 2019/02/11 19:56 by mmacgregor

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki