NFS ( Network file system ) Configuration in linux step by step rhel6 and create users ... - 0 views
-
munna1357 on 06 Jun 16At present, there are three variants of NFS. NFS form 2 (NFSv2) is more established and generally bolstered. NFS form 3 (NFSv3) underpins safe nonconcurrent composes and is more hearty at mistake taking care of than NFSv2; it likewise bolsters 64-bit record sizes and balances, permitting customers to get to more than 2Gb of document information. NFS form 4 (NFSv4) works through firewalls and on the Internet, no more requires a rpcbind administration, bolsters ACLs, and uses stateful operations. Red Hat Enterprise Linux 6 underpins NFSv2, NFSv3, and NFSv4 customers. At the point when mounting a document framework through NFS, Red Hat Enterprise Linux utilizes NFSv4 as a matter of course, if the server underpins it. All forms of NFS can utilize Transmission Control Protocol (TCP) running over an IP system, with NFSv4 requiring it. NFSv2 and NFSv3 can utilize the User Datagram Protocol (UDP) running over an IP system to give a stateless system association between the customer and server. At the point when utilizing NFSv2 or NFSv3 with UDP, the stateless UDP association (under typical conditions) has less convention overhead than TCP. This can interpret into better execution on clean, non-congested systems. In any case, on the grounds that UDP is stateless, if the server goes down suddenly, UDP customers keep on saturating the system with solicitations for the server. Moreover, when a casing is lost with UDP, the whole RPC ask for must be retransmitted; with TCP, just the lost casing should be loathe. Consequently, TCP is the favored convention when associating with a NFS server. -
munna1357 on 06 Jun 16At present, there are three variants of NFS. NFS form 2 (NFSv2) is more established and generally bolstered. NFS form 3 (NFSv3) underpins safe nonconcurrent composes and is more hearty at mistake taking care of than NFSv2; it likewise bolsters 64-bit record sizes and balances, permitting customers to get to more than 2Gb of document information. NFS form 4 (NFSv4) works through firewalls and on the Internet, no more requires a rpcbind administration, bolsters ACLs, and uses stateful operations. Red Hat Enterprise Linux 6 underpins NFSv2, NFSv3, and NFSv4 customers. At the point when mounting a document framework through NFS, Red Hat Enterprise Linux utilizes NFSv4 as a matter of course, if the server underpins it. All forms of NFS can utilize Transmission Control Protocol (TCP) running over an IP system, with NFSv4 requiring it. NFSv2 and NFSv3 can utilize the User Datagram Protocol (UDP) running over an IP system to give a stateless system association between the customer and server. At the point when utilizing NFSv2 or NFSv3 with UDP, the stateless UDP association (under typical conditions) has less convention overhead than TCP. This can interpret into better execution on clean, non-congested systems. In any case, on the grounds that UDP is stateless, if the server goes down suddenly, UDP customers keep on saturating the system with solicitations for the server. Moreover, when a casing is lost with UDP, the whole RPC ask for must be retransmitted; with TCP, just the lost casing should be loathe. Consequently, TCP is the favored convention when associating with a NFS server.
