Filesystems Size

[Ila Nigam]

Is there any recommended size for basic filesystems on vg00 ???
ex - /, /usr, /var, /opt etc.

Any white paper from HP for reference?

[S.K. Chan · Accepted solution]

The white paper you need ..

http://docs.hp.com/hpux/onlinedocs/5963-8942/5963-8942.html

[James R. Ferguson]

Hi:

Your size needs will vary. On 11.0 the defaults I've seen look like this:

/stand 84
/ 140
/home 20
/opt 256
/tmp 64
/usr 500
/var 500

I find these far too small. I like to keep a few extra kernels in /stand, so I increase that. Enlarging /tmp is quite important when you want to download and apply patches. A larger /var is a must for software installation and the Installed Products Database (IPD) as successive patch applications (via 'swinstall') occur. Here is what I like as a minimum:

/stand 140
/ 140
/home 100
/opt 1000
/tmp 500
/usr 1500
/var 1500

Regards!

...JRF...

[A. Clay Stephenson]

Hi:

I would more or less agree with JRF's numbers but I would add that the three that are really important are /, /stand, and primary swap. These must be contigiuos and can't (easily) be resized after install. All of the other filesystems can be enlarged later. If you go ahead and make / and /stand 140MB or so each, then future OS upgrades and patches are much easier. By the way, you can get by with a rather small primary swap (256MB) even with a machine that has a large amount of memory. Primary swap is required; it just doesn't have to very big. You can then have additional swap elsewhere if needed or desired.

Regards, Clay

[Ila Nigam]

Having a single filesystem / of entire disk space excluding the swap area, is a good idea ? Any pros and cons of it ???


Thanks.

[Helen French]

Hi,

Check this :
http://www.docs.hp.com/cgi-bin/onlinedocs.py?mpn=5963-8942&service=hpux&path=../5963-8942/00/00/1&title=HP-UX%2010.0%20File%20System%20Layout%20White%20Paper

HTH,
Shiju

[A. Clay Stephenson]

Hi Ila:

Bad idea. In the first place, you must have a separate /stand becuase it has to be an hfs filesystem. The others can be vxfs or hfs. The only possible advantage to using the rest as / is the illusion that adminstration becomes easier. First of all, with very minor exceptions, / should not increase in size at all over time. Secondly, you can achieve very flexible layouts by leaving a fair amount of space unconfigured and then extending the logical volumes and filesystems later. This becomes a trivial task if you have OnlineJFS. Really no HP-UX server should be without it. Believe me, the very last thing you want is an absolutely full root filesystem and that is just what you are setting yourself up for.
One other thing to consider is that only /stand, /, and primary swap have to be on the boot disk. The other filesystems can be anywhere and don't even have to be on vg00. I'm not saying that this is a good idea, it is just a way to give you more options.

Clay

[S.K. Chan]

Personally (from my experience) having / and /stand only works great if you have 1000 HP-UX workstations to manage. We use Ignite-UX process to installed OS on these clients. However on the servers we have a mix of both configuration.