However, a system administrator can choose to add or delete exports Of /etc/exports and files under /etc/exports.d by invoking exportfs -a. Normally the master export table is initialized with the contents This file is read by rpc.mountd when a client sends The master export table is kept in a file named The exportfs command maintains the current table of exports for the NFS To as an exported file system, or export, for short. Each file system in this table is referred Since rpc.mountd refers to the xtab file when deciding access privileges to a file system, changes to the list of exported file systems take effect immediately.Īlso read the exportfs man page for more details, specifically the "DESCRIPTION" section which explains all this and more.Īn NFS server maintains a table of local physical file systems that areĪccessible to NFS clients. When given the proper options, the /usr/sbin/exportfs command writes the exported file systems to /var/lib/nfs/xtab. When issued manually, the /usr/sbin/exportfs command allows the root user to selectively export or unexport directories without restarting the NFS service. All that's required is to issue the appropriate command after editing the /etc/exports file: $ exportfs -raĮxcerpt from the official Red Hat documentation titled: 21.7. You shouldn't need to restart NFS every time you make a change to /etc/exports. That means, whenever i make the changes in /etc/exports and restart the service, i will need to go RE-MOUNT the directories on EVERY CLIENTS in the export list, in order to have the mount-points working again. If i service nfs restart, why the Mount-Point on other Clients are eventually affected? (For those Client Machines with NO changes made in /etc/exports for them.).Whenever i modify the /etc/exports, should i restart the service or what?.Everything for the client-1 are still untouched. (Why? Because of RESTART?)īut as described, i only modified the line for client-2 only. the mount-point on client-1 got unresponsive (Can't open its files, etc). shares/xxxxxxxx (rw,sync,no_subtree_check,no_root_squash) Then whenever i made some changes in that (let's say the changes ONLY for client-2), e.g: /shares/website1 (rw,sync,no_subtree_check,no_root_squash) shares/website2 (rw,sync,no_subtree_check,no_root_squash) Let's say in /etc/exports: /shares/website1 (rw,sync,no_subtree_check,no_root_squash) I have NFSv4 Server (on RHELv6.4) and NFS Clients on (CentOSv6.4).