- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: TruCluster separate /usr/tmp filesystem
Operating System - Tru64 Unix
1752782
Members
6269
Online
108789
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-31-2008 03:15 AM
тАО07-31-2008 03:15 AM
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
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 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-31-2008 04:13 AM
тАО07-31-2008 04:13 AM
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.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-01-2008 07:56 AM
тАО08-01-2008 07:56 AM
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.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP