Clonfs1 - Revision history

Boiarino at 19:07, 15 April 2024

2024-04-15T19:07:19Z

2024-02-06T19:23:03Z

← Older revision		Revision as of 15:23, 6 February 2024
Line 6:		Line 6:
	you may need to touch ''exports'' file before and after running ''exportfs -a'' in following section, to enforce mounting permissions propagation		you may need to touch ''exports'' file before and after running ''exportfs -a'' in following section, to enforce mounting permissions propagation

	ssh ~~root@clon10 (old Solaris machine)~~		ssh -c 3des-cbc root@clonfs1a-old
	~~ssh~~ root@clonfs1a-old
	exportfs -a		exportfs -a
	modify ''exports'' in above section		modify ''exports'' in above section

2024-02-06T19:19:28Z

← Older revision		Revision as of 15:19, 6 February 2024
Line 1:		Line 1:
			'''/work disk file server'''

			ssh root@clon00
			cd /mnt/admin/clonfs1a-old/etc
			add desired machine to the file ''netgroup''
			you may need to touch ''exports'' file before and after running ''exportfs -a'' in following section, to enforce mounting permissions propagation

			ssh root@clon10 (old Solaris machine)
			ssh root@clonfs1a-old
			exportfs -a
			modify ''exports'' in above section
			exportfs -a
			modify ''exports'' back to original




			'''WAS: Main file server'''

	Clonfs1 is the main file server for the clon cluster. It holds /home, /local etc directories for all clon machines.		Clonfs1 is the main file server for the clon cluster. It holds /home, /local etc directories for all clon machines.

2017-09-26T19:34:03Z

← Older revision		Revision as of 15:34, 26 September 2017
Line 6:		Line 6:

	* to increase volume size on 50G: vol size <volume_name> +50g		* to increase volume size on 50G: vol size <volume_name> +50g

			* to check if partition is actually exported to particular machine, go to that machine or any other machine and type:

			DO NOT KNOW HOW ...

	* if partition exported but machines has problem mounting it, use following example where machine '129.57.167.184' could not mount:		* if partition exported but machines has problem mounting it, use following example where machine '129.57.167.184' could not mount:

2016-10-11T20:34:12Z

← Older revision		Revision as of 16:34, 11 October 2016
Line 6:		Line 6:

	* to increase volume size on 50G: vol size <volume_name> +50g		* to increase volume size on 50G: vol size <volume_name> +50g

			* if partition exported but machines has problem mounting it, use following example where machine '129.57.167.184' could not mount:

			exportfs -c 129.57.167.184 /vol/logs
			exportfs: 129.57.167.184 does not have mount access to /vol/logs (Access denied)
			exportfs -f /vol/logs
			exportfs -c 129.57.167.184 /vol/logs
			exportfs: 129.57.167.184 has mount access to /vol/logs

	* use 'help' to see all commands		* use 'help' to see all commands

2016-03-31T18:02:30Z

← Older revision		Revision as of 14:02, 31 March 2016
Line 1:		Line 1:
	Clonfs1 is the main file server for the clon cluster. It holds /home, /local etc directories for all clon machines. It can be managed using link http://clonfs1/na_admin/. Its ''/etc'' directory and volumes are mounted on clon00 and clon10 under ''/mnt/admin''.		Clonfs1 is the main file server for the clon cluster. It holds /home, /local etc directories for all clon machines.

			To manage, 'ssh root@clonfs1' and do following:

			* to export partitions: 'exportfs -a'

			* to increase volume size on 50G: vol size <volume_name> +50g

			* use 'help' to see all commands



			OBSOLETE: It can be managed using link http://clonfs1/na_admin/. Its ''/etc'' directory and volumes are mounted on clon00 and clon10 under ''/mnt/admin''.

	'''NOTE''': if exporting ''hostname'' is not registered officially (does not recognized by ''nslookup''), it must be described in clonfs1's ''/etc/hosts'' file !		'''NOTE''': if exporting ''hostname'' is not registered officially (does not recognized by ''nslookup''), it must be described in clonfs1's ''/etc/hosts'' file !

2013-08-30T17:54:59Z

← Older revision		Revision as of 13:54, 30 August 2013
Line 12:		Line 12:

	'''clas (backup by CC)''' - contains clas-specific contents (''/usr/clas/parms'', ''/usr/clas/devel'' etc)		'''clas (backup by CC)''' - contains clas-specific contents (''/usr/clas/parms'', ''/usr/clas/devel'' etc)

			'''clas12 (backup by CC)''' - contains clas12-specific contents (''parms'', ''coda'' etc)

	'''clonweb (backup by CC)''' - directory mounted on ''clonweb'' machine as ''/www''		'''clonweb (backup by CC)''' - directory mounted on ''clonweb'' machine as ''/www''

2013-08-30T17:53:38Z

← Older revision		Revision as of 13:53, 30 August 2013
Line 56:		Line 56:
	/vol/downloads -sec=sys,rw=clons,anon=0		/vol/downloads -sec=sys,rw=clons,anon=0
	/vol/clas -sec=sys,rw=clons,anon=0		/vol/clas -sec=sys,rw=clons,anon=0
			/vol/clas12 -sec=sys,rw=clons,anon=0
	/vol/apps -sec=sys,rw=clons,anon=0		/vol/apps -sec=sys,rw=clons,anon=0
	/vol/work -sec=sys,rw=clons,anon=0		/vol/work -sec=sys,rw=clons,anon=0

2012-01-02T21:12:21Z

← Older revision		Revision as of 17:12, 2 January 2012
Line 3:		Line 3:
	'''NOTE''': if exporting ''hostname'' is not registered officially (does not recognized by ''nslookup''), it must be described in clonfs1's ''/etc/hosts'' file !		'''NOTE''': if exporting ''hostname'' is not registered officially (does not recognized by ''nslookup''), it must be described in clonfs1's ''/etc/hosts'' file !

	'''NOTE''': after changing ''/etc/netgroup'' or ''/etc/exports'' (see below) do ''ssh root@clonfs1'' and execute command ''exportfs -a''. If not exported, try following trick: add some existing machine (clon10 for example) to the ''/etc/exports'' to all entries, and do ''exportfs -a''. Next time change clon10 to clon00, ~~end~~ so on.		'''NOTE''': after changing ''/etc/netgroup'' or ''/etc/exports'' (see below) do ''ssh root@clonfs1'' and execute command ''exportfs -a''. If not exported, try following trick: add some existing machine (clon10 for example) to the ''/etc/exports'' to all entries, and do ''exportfs -a''. Next time change clon10 to clon00, and so on.

	Clonfs1 has following volumes:		Clonfs1 has following volumes:

2011-11-15T18:40:39Z

← Older revision		Revision as of 14:40, 15 November 2011
Line 2:		Line 2:

	'''NOTE''': if exporting ''hostname'' is not registered officially (does not recognized by ''nslookup''), it must be described in clonfs1's ''/etc/hosts'' file !		'''NOTE''': if exporting ''hostname'' is not registered officially (does not recognized by ''nslookup''), it must be described in clonfs1's ''/etc/hosts'' file !

			'''NOTE''': after changing ''/etc/netgroup'' or ''/etc/exports'' (see below) do ''ssh root@clonfs1'' and execute command ''exportfs -a''. If not exported, try following trick: add some existing machine (clon10 for example) to the ''/etc/exports'' to all entries, and do ''exportfs -a''. Next time change clon10 to clon00, end so on.

	Clonfs1 has following volumes:		Clonfs1 has following volumes: