Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
Operating System - Tru64 Unix
cancel
Showing results for 
Search instead for 
Did you mean: 

TruCluster separate /usr/tmp filesystem

Ian Croft
Occasional Contributor

TruCluster separate /usr/tmp filesystem

Does anyone know any reason why I shouldn't be able to create a separate /usr/tmp filesystem in my five node TruCluster ? And if there are any gotchas or files other than /etc/fstab that I would need to update ?

i.e. Change this layout
cluster_root#root 4480M 556M 3924M 13% /
cluster_usr#usr 8000M 2727M 5253M 35% /usr
cluster_var#var 8000M 4574M 3410M 58% /var

to be this :-
cluster_root#root 4480M 556M 3924M 13% /
cluster_usr#usr 8000M 2727M 5253M 35% /usr
cluster_usrtmp#usrtmp 8000M 2727M 5253M 35% /usr/tmp
cluster_var#var 8000M 4574M 3410M 58% /var
2 REPLIES
Vladimir Fabecic
Honored Contributor

Re: TruCluster separate /usr/tmp filesystem

There is no reason why you shouldn't be able to create a separate /usr/tmp filesystem.
You have to update just /etc/fstab.

But, why do you need it for?
For tmp directory?
Why /usr/tmp and not /tmp ?
Do not forget that /tmp is cluster dependent symbolic link (CDSL).
It is not good to have same directory for tmp for all cluster members.
In vino veritas, in VMS cluster
Hein van den Heuvel
Honored Contributor

Re: TruCluster separate /usr/tmp filesystem


It is fine to have the setup, but how will it be used? Directly as /usr/tmp or from a (soft)link from /tmp

When I saw /usr/tmp being used it was often the target of a softlink for /tmp.

You want your /tmp to be node independent, in case a non-cluster-aware application decides it knows it is the only job creating a certain tmp file.... not any more.

So instead of just 1 of those, you may want to create as many directotries and filesets as you have members:

cluster_usrtmp#usrtmp /usr/tmp
cluster_usrtmp#usrtmp0 /usr/tmp0
cluster_usrtmp#usrtmp1 /usr/tmp1

That would not 'cost' anything more, the same domain and diskblocks being used, but it allows cluster members to 'see' only their own /tmp.

An earlier note on this:

http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=847533

You may want to hook that extended space behind: /cluster/members/memberX/tmp


hth,
Hein.