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

Explain the tools used to monitor system security.

12.Explain the tools used to monitor system security. Ans. 1. People who, for purpose of larceny or to amuse themselves, like to break into computers, they are called ‘crackers’. 2. If there is a vulnerability in a system they will find it and use it against you. 3. Preventing use of your machine for nefarious purpose and guarding against intrusion are, in the end, your responsibility alone. 4. Red hat equips you with tools to detect and deal with unauthorised access of many kinds. 5. You need to configure those tools and understand how to sense the warning they provide. 6. Fortunately Linux is development community is quick to find potential exploits and to create ways of slamming the doors before crackers can enter in your system. 7. Red hat is careful enough to making available new, patched version in which potential exploits have been found. 8. You should make sure to download and install the repaired package. 9. This line of defence...

Explain memory and virtual file system in Linux.

22.Explain memory and virtual file system in Linux. Ans. 1. These file systems do not exist on disk in the same way that traditional file systems do, they either exists entirely in the system memory or they are virtual because they are an interface to system devices. 2. cramfs: cramfs is designed to cram a file System onto a small flash memory device, so it is small, simple and able to compress things well. The largest file size is 16MB and the largest file system size is 256MB since cramfs is so compressed, it isn’t instantly updateable. 3. tmpfs: tmpfs is structured around the idea that whatever is put in the /tmp file system is accessed again shortly, tmpfs solely in memory, so what you put in /tmp doesn’t persist between reboots. 4. ramfs: ramfs is basically cramfs without the compression. 5. romfs: This is a read only file system that is mostly used for initial ramdisks of installation disks. It was designed to take up very little space, so you could fit a ke...

Explain how to configure DHCP client?

50.Explain how to configure DHCP client? Ans. 1. Before configuring DHCP, NIC should be configured properly and recognized by the system. 2. After that it’s easy to command system to use DHCP to obtain its IP information. 3. Configuring DHCP client involves following steps : a. Open the /etc/sysconfig/networkscripts/ifcfg-eth0 file. b. Find the line bootproto=static c. Change the static to dhcp. d. Save changes. e. Restart the network by issuing command ‘service network restart’, after that system will receive its IP information from the DHCP server.