Skip to main content

What are the disadvantages of Network file system (NFS)?

58.What are the disadvantages of Network file system (NFS)?
Ans.
1. NFS is sensitive to network congestion/traffic which shows down NFS performance.

2. Busy disk activity on the NFS server badly affects NFS’s performance.

3. The performance enhancement incorporated in NFSv4 have increased NFS’s stability and reliability on high latency and heavily congested networks.

4. If user/client wants to mount some files which is not exported, then client’s system may get hang and this can be resolved with the help of mount option.

5. Is the disk or system exporting important data or application becomes unavailable, such as a disk crash or server failure, no one can access that resource.

6. NFS suffers from potential security problems because its designs assure a trusted networks.

7. The major weakness of most NFS implementation based on protocol’s other versions, that they are based on standard RPC which is unencrypted.

8. Sensitive information should never be exported from or mounted on systems directly exposed to the internet.

Comments

  1. Many of the security points raised here refer to NFS 3.0; NFS 4.0 (and later) have better security and require encryption of both the user credentials and the data transferred (points #6/7/8).
    Also why is point #3 a disadvantage?

    ReplyDelete
    Replies
    1. #3 is on Disadvantage of older versions of NFS over newer versions and the answer is abstract over all NFS versions its not version specific that's why i didn't mention version in question. i agree most of the points are centred at older version but newer versions are not flawless either.

      Delete

Post a Comment

Popular posts from this blog

Java,ES,QT practical files

All practical files: Click below to start download Uploaded on special request||||

How to configure Network file system version 4 (NFSv4) client?

69.How to configure Network file system version 4 (NFSv4) client? Ans. 1. There are two new options listed in NFSv4 are introduced as: clientaddr and ports 2. The version 3 of NFS introduced NFS over TCP, which improved NFS’s reliability. 3. In NFSv3, users use the mount option i.e., tcp as client whether client wants to use TCP or UDP to communicate with the server. NFSv4 replaces tcp or udp with a single option i.e. ports=tcp or udp 4. The default buffer size for NFSv4 is 8192 bytes, but it can grow to as large and by 32,678 bytes, which results performance improvements. 5. Following are the mount options: clientaddr=n – Declares client to be multihomed proto=type – Declares port as either udp or tcp resize=n – declares read size of clients buffer wsize=n – Declares write size of clients buffer sec=mod – Declares security model as either krb, krb5 etc.

Absolute Links vs. Relative Links – SEO Value

Absolute Links vs. Relative Links – SEO Value The debate between  absolute links and relative links  continues to live on in the SEO world. The individual significance of each has been contested, but it is widely regarded that absolute links provide better SEO value on the whole than relative links. Many believe that absolute links have less potential for getting messed up when search engines index your page. It shouldn’t really make a difference, but many conclude that this is reason enough. Read more...