NFS - Revision history

Craigje at 21:05, 14 July 2021

2021-07-14T21:05:47Z

← Older revision		Revision as of 21:05, 14 July 2021
Line 23:		Line 23:
	* look for the right line in <code>/etc/fstab</code> - something like <code>159.28.22.31:/smiley-eccs-home-disk/eccs /eccs nfs auto,nofail,noatime,nolock,intr,tcp,actimeo=1800 0 2</code>.		* look for the right line in <code>/etc/fstab</code> - something like <code>159.28.22.31:/smiley-eccs-home-disk/eccs /eccs nfs auto,nofail,noatime,nolock,intr,tcp,actimeo=1800 0 2</code>.

	= ~~Allowing NFS in a firewall~~ =		= Notes for sysadmins =

	~~Few of our servers~~ run a ~~firewall, but the cluster head nodes do (as of this writing)~~. ~~You want to make sure to allow calls to mount NFS, thusly:~~		There's a lot more about how we run NFS to be found [[Sysadmin:NFS\|here]] if you are a sysadmin.
	~~<pre>~~
	~~firewall-cmd --permanent --add-service=nfs~~
	~~firewall-cmd --permanent --add-service=mountd~~
	~~firewall-cmd --permanent --add-service=rpc-bind~~
	~~firewall-cmd --reload~~
	~~</pre>~~

Craigje at 17:04, 26 May 2021

2021-05-26T17:04:16Z

← Older revision		Revision as of 17:04, 26 May 2021
Line 1:		Line 1:
	We use NFS to share files (e.g. software, user home directories) across computers in the CS and cluster domains. This page will be largely informed by CS-side information, but much of it will carry over into the cluster world as well.		We use NFS to share files (e.g. software, user home directories) across computers in the CS and cluster domains. This page will be largely informed by CS-side information, but much of it will carry over into the cluster world as well.

	On the CS side, the main NFS server is ~~smiley, though we also use tools as an NFS server for software~~. On the cluster side, the main NFS server is ~~hopper~~.		On the CS side, the main NFS server is bowie. On the cluster side, the main NFS server is hopperprime. Each cluster head node also has NFS exports. (This is not a comprehensive list.)

	= Files =		= Files =

	For the common pattern of <code>/etc/exports</code> and <code>/etc/fstab</code>, see [[Lovelace \| how we mount software directories on Lovelace]]. There's nothing particularly special about the case of the Lovelace machines, so the pattern should largely hold up across our servers.		For the common pattern of <code>/etc/exports</code> and <code>/etc/fstab</code>, see [[Lovelace \| how we mount software directories on Lovelace]]. There's nothing particularly special about the case of the Lovelace machines, so the pattern should largely hold up across our servers: list the directories you wish to export from the local system in <code>/etc/exports</code> and the directories/disks you wish to mount in <code>/etc/fstab</code>.

	= User directory troubleshooting =		= User directory troubleshooting =

	When a user logs in to one of our computers, they should land in a home directory. These are stored one machine in each subdomain and exported to the other machines by NFS. In the CS case, the home directories are stored on ~~smiley~~.		When a user logs in to one of our computers, they should land in a home directory. These are stored one machine in each subdomain and exported to the other machines by NFS. In the CS case, the home directories are stored on bowie.

	One possible problem with user logins on machines other than smiley (i.e. any machine most people will try to access) is that the directories haven't been mounted. This should be done automatically but was not, for some time. We believe we've solved it but have placed this guide here for reference. Consult it, for example, if...		One possible problem with user logins on machines other than smiley (i.e. any machine most people will try to access) is that the directories haven't been mounted. This should be done automatically but was not, for some time. We believe we've solved it but have placed this guide here for reference. Consult it, for example, if...
Line 19:		Line 19:

	To check if there's a problem with how we're handling NFS mounting of user directories, and if so to fix it, do the following:		To check if there's a problem with how we're handling NFS mounting of user directories, and if so to fix it, do the following:
	* run <code>df -h</code> to see what filesystems are mounted; as of August 2018, for example, you should see a line resembling <code>~~159~~.28.22.31:/~~smiley-eccs-home-disk~~/eccs 4.0T 1.2T 2.7T 31% /eccs</code>. If so, your problem probably isn't here. If not, proceed.		* run <code>df -h</code> to see what filesystems are mounted; as of August 2018, for example, you should see a line resembling <code>10.10.10.15:/earlhamcs/eccs 4.0T 1.2T 2.7T 31% /eccs</code>. If so, your problem probably isn't here. If not, proceed.
	* run <code>sudo mount -a</code> and then <code>df -h</code>. If the problem persists, proceed.		* run <code>sudo mount -a</code> and then <code>df -h</code>. If the problem persists, proceed.
	* look for the right line in <code>/etc/fstab</code> - something like <code>159.28.22.31:/smiley-eccs-home-disk/eccs /eccs nfs auto,nofail,noatime,nolock,intr,tcp,actimeo=1800 0 2</code>.		* look for the right line in <code>/etc/fstab</code> - something like <code>159.28.22.31:/smiley-eccs-home-disk/eccs /eccs nfs auto,nofail,noatime,nolock,intr,tcp,actimeo=1800 0 2</code>.

			= Allowing NFS in a firewall =

			Few of our servers run a firewall, but the cluster head nodes do (as of this writing). You want to make sure to allow calls to mount NFS, thusly:
			<pre>
			firewall-cmd --permanent --add-service=nfs
			firewall-cmd --permanent --add-service=mountd
			firewall-cmd --permanent --add-service=rpc-bind
			firewall-cmd --reload
			</pre>

Craigje: Created page with "We use NFS to share files (e.g. software, user home directories) across computers in the CS and cluster domains. This page will be largely informed by CS-side information, but..."

2018-08-01T13:46:19Z

Created page with "We use NFS to share files (e.g. software, user home directories) across computers in the CS and cluster domains. This page will be largely informed by CS-side information, but..."

New page

We use NFS to share files (e.g. software, user home directories) across computers in the CS and cluster domains. This page will be largely informed by CS-side information, but much of it will carry over into the cluster world as well.

On the CS side, the main NFS server is smiley, though we also use tools as an NFS server for software. On the cluster side, the main NFS server is hopper.

= Files =

For the common pattern of <code>/etc/exports</code> and <code>/etc/fstab</code>, see [[Lovelace | how we mount software directories on Lovelace]]. There's nothing particularly special about the case of the Lovelace machines, so the pattern should largely hold up across our servers.

= User directory troubleshooting =

When a user logs in to one of our computers, they should land in a home directory. These are stored one machine in each subdomain and exported to the other machines by NFS. In the CS case, the home directories are stored on smiley.

One possible problem with user logins on machines other than smiley (i.e. any machine most people will try to access) is that the directories haven't been mounted. This should be done automatically but was not, for some time. We believe we've solved it but have placed this guide here for reference. Consult it, for example, if...
* you receive bizarre login messages
* you don't see your user files on login
* you expect to authenticate via ssh keys but you end up having to use your Unix password instead

(This guide does assume you can log in somehow, at least as sysadmin or at the console.)

To check if there's a problem with how we're handling NFS mounting of user directories, and if so to fix it, do the following:
* run <code>df -h</code> to see what filesystems are mounted; as of August 2018, for example, you should see a line resembling <code>159.28.22.31:/smiley-eccs-home-disk/eccs 4.0T 1.2T 2.7T 31% /eccs</code>. If so, your problem probably isn't here. If not, proceed.
* run <code>sudo mount -a</code> and then <code>df -h</code>. If the problem persists, proceed.
* look for the right line in <code>/etc/fstab</code> - something like <code>159.28.22.31:/smiley-eccs-home-disk/eccs /eccs nfs auto,nofail,noatime,nolock,intr,tcp,actimeo=1800 0 2</code>.