topic Re: OS FileSystem Sizes in Operating System - HP-UX

OS FileSystem Sizes

Aaron_4 — Wed, 28 May 2003 13:21:50 GMT

Is there a standard practice for OS Filesystem sizes in 11i. Since the systems we are getting have 4X36 gig drives I was just wondering if there is a standard that is recommended by HP.

thanks
aaron

Re: OS FileSystem Sizes

Frederic Sevestre — Wed, 28 May 2003 13:27:39 GMT

Hi,

I don't know if there is a standart parctice but here is a copy of what we are using for our servers under 11i

Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 204800 76576 127264 38% /
/dev/vg00/lvol1 298928 57920 211112 22% /stand
/dev/vg00/lvol10 2097152 653408 1432728 31% /var
/dev/vg00/lvol11 2097152 59579 1910266 3% /var/adm/crash
/dev/vg00/lvol9 1540096 968896 566776 63% /usr
/dev/vg00/lvol8 516096 4064 508592 1% /tmp
/dev/vg00/lvol6 1048576 744920 301344 71% /opt
/dev/vg00/lvol4 1048576 5888 1034608 1% /home

Regards,
Fr??d??ric

Re: OS FileSystem Sizes

A. Clay Stephenson — Wed, 28 May 2003 13:36:37 GMT

This is purely me and I go in with the knowledge that most of the time when initially setting up a box that "I don't know what I don't know" - meaning that often the applications and data requirements are not very well defined initially. My approach is to be rather generous on the /stand and / (which can't be extended later) and don't worry about the others - which can be easily extended.

I would typically size /stand at around 160-200MB and / at 200-256MB. Primary swap must be at least 256MB but in your case I would probably go for 1GB.

In your case, I would start with /usr at about 1GB, /var at about 1GB, and /opt at about 1GB. /home and /tmp - season to taste.

The best advice I can give is to mirror the boot disk and make sure that OnlineJFS is available. It's then so easy to extend the LVOL's/filesystems and add additional swap that you really don't need to worry about it.

I would only use two of these disks for vg00 and leave the others unused at this time.

Re: OS FileSystem Sizes

Patrick Wallek — Wed, 28 May 2003 13:55:48 GMT

My preferences:

/ and /stand - 256 MB
/var, /usr, and /opt - 3 GB
/tmp and /home - entirely up to you

You could get away with having /var smaller if you split /var/adm/sw into it's own LVOL. In that case I might do /var at 1GB and /var/adm/sw at 2GB.

Re: OS FileSystem Sizes

James R. Ferguson — Wed, 28 May 2003 13:58:14 GMT

Hi Arron:

Minimum file sysstem sizes are dependent on the OE variant of 11i you are using and on *your* requirements.

Be generous when you size '/var', '/tmp' and /'opt'. Remember that 'var' is going to grow as you patch. '/tmp' is where (standardly) patch depots are created. '/opt' can require less or more space depending on products you install (Ansi C, for instance).

See here for more information:

http://docs.hp.com/hpux/onlinedocs/5187-1350/5187-1350.html

Regards!

...JRF...

Re: OS FileSystem Sizes

Pete Randall — Wed, 28 May 2003 13:58:19 GMT

Aaron,

The only HP recommendations I've seen are minimums. The other common recommendation is to keep your root volume (VG00) separate from your other data volumes. I'm not quite sure how you do that with 4X36GB drives. I wasted quite a bit of space on 18GB drives in order to keep it restricted to just VG00.

As far as individual file system sizes, it depends. If you'll be loading lots of apps, make /opt and /usr big (like 1GB and 2GB, respectively). Make /var big - that's where most of the growth from logs and patching ends up (like 2GB or 4GB, anyway). Other stuff can remain relatively small - here's my layout:

bdfmegs -l |grep vg00
/dev/vg00/lvol3 200 40 150 21% /
/dev/vg00/lvol1 93 29 55 34% /stand
/dev/vg00/lvol8 11552 4476 6872 39% /var
/dev/vg00/lvol7 800 613 175 78% /usr
/dev/vg00/lvol6 64 16 46 25% /tmp
/dev/vg00/lvol5 2000 1760 225 89% /opt
/dev/vg00/lvol4 600 222 355 38% /home

Pete

Re: OS FileSystem Sizes

Geoff Wild — Wed, 28 May 2003 14:00:17 GMT

Here's what we do:

Vgcreate volume groups as per the following standard
Preamble: VG00 - VG09 are internal disks, VG10 and higher are reserved for EMC.
VG00
The root volume group VG00 should be mirrored and only contain OS files.
Primary swap should be 1 x memory
/ - 200
/usr - 1GB
/var - 1GB
/tmp - 512MB
/stand - 128MB
/var/adm/crash - 1 x memory + 512MB
/opt - 1GB
/home - 512MB with quotas (32MB soft, 64MB hard)
Note: /var/tmp should be a symbolic link to /tmp. /tmp should be 1777 (sticky bit).
VG01
/app - 512MB
/usr/local - 512MB
/app/admin - 512MB
VG02
File system swap
VG03
Applications
VG04-VG09
Reserved
VG10 - VG19
Log volumes (redo, archive, etc)
VG20 - VG256
Data volumes

Miscellaneous
Don't use strict/contiguous when creating logical volumes.
Create file systems with "large file" support (fsadm).
Mount file systems with "delaylog".
Oracle
The following is the typical oracle layout:
Volume Size File System
vg01 4 Gig - /app/oracle
vg01 500 Meg - /app/dbcorp
vg30 4 Gig - /data/oracle/irsp/data01 vg30 6 Gig - /data/oracle/irsp/data02 vg30 6 Gig - /data/oracle/irsp/data03 -----------> Can all be on one mount point if need be, logical directory separation required
vg30 6 Gig - /data/oracle/irsp/data04 / though.
vg12 12 Gig - /data/oracle/irsp/arch ----> on different physical volumes than .../dataxx & .../redoxx mount points
vg10 8 Gig - /data/oracle/irsp/exports ----> on different physical volumes than .../dataxx mount points
vg31 2 Gig - /data/oracle/irsp/indx01 vg31 2 Gig - /data/oracle/irsp/indx02 vg31 2 Gig - /data/oracle/irsp/indx03 -----------------> Can all be on one mount point if need be, but on different physical
vg31 2 Gig - /data/oracle/irsp/indx04 / volumes than ...../dataxx mount points.
vg31 2 Gig - /data/oracle/irsp/indx05 /
vg10 1.5 Gig - /data/oracle/irsp/redo01a
vg11 1.5 Gig - /data/oracle/irsp/redo01b ----> redo01a & redo01b on different physical volumes
vg10 1.5 Gig - /data/oracle/irsp/redo02a
vg11 1.5 Gig - /data/oracle/irsp/redo02b ----> redo02a & redo02b on different physical volumes

APPENDIX F - Kernel Parameters

Parameter Value Description
MAXVG 256 Maximum number of volume groups
MAXFILES 2048 Soft limit on how many files a single process can have opened or locked at any given time.
NFILE 4096 Maximum number of files that can be open simultaneously on the system at any given time.
NINODE 20000 Maximum number of open inodes that can be in memory.
MSGSEG 4096 Maximum number of message segments that can exist on the system.
NPROC 1024 Defines the maximum number of processes that can be running simultaneously on the entire system, including remote execution processes initiated by other systems via remsh or other networking commands.
SHMMAX 1073741824 Maximum allowable shared memory segment size (in bytes).
SHMMNI 100 Maximum number of shared memory segments allowed on the system at any given time.
SEMMNS 500 Maximum number of individual IPC semaphores available to system users, system-wide.
SHMSEG 10 Maximum number of shared memory segments that can be attached simultaneously to any given process.
DBC_MAX_PCT 10 Maximum percentage of memory for dynamic buffer cache

Re: OS FileSystem Sizes

Martin Johnson — Wed, 28 May 2003 14:03:15 GMT

If you are using vxfs file systems, the only one you really have to worry about is /stand becuase it cannot be vxfs. It is hfs and contiguous. Therefore, it cannot easily be extended. Usually, you have to do an Ignite backup and recovery to change the size of /stand.

Using vxfs file systems will allow you to extend the file systems without a reboot. Use the recommendations given in the previous replies and keep a couple of GBs in reserve to use in extending file systems when needed.

HTH
Marty

Re: OS FileSystem Sizes

Massimo Bianchi — Wed, 28 May 2003 14:04:00 GMT

Hi,
rememeber to have at least 500Mb
fot /tmp, otherwise many sw installation are problematic.

If you plan to have a 64bit oracle with SAP, usually there must be 20Gb swap (!!).

Massimo

Re: OS FileSystem Sizes

Aaron_4 — Wed, 28 May 2003 14:15:59 GMT

Thanks for the advise. The new servers should start coming in tomorrow.

Re: OS FileSystem Sizes

Steve Valvasori — Thu, 29 May 2003 10:42:59 GMT

I just want to tack on one thing that Geoff touched on in his post. You should ensure that /var/adm/crash has enough space, preferably it's own FS. Nothing sucks more than management asking why a box paniced, and you don't have a complete dump to analyze.

Steve.

Re: OS FileSystem Sizes

Yogeeraj_1 — Thu, 29 May 2003 12:00:37 GMT

hi aaron,

Our main file systems on our production servers have been configured as follows:

home/yd> /home/yd/bdfmegs
File System Mbytes Used Avail %Used Mounted on
/dev/vg00/lvol3 200 96 103 48% /
/dev/vg00/lvol1 288 52 207 20% /stand
/dev/vg00/lvol8 4096 912 3161 22% /var
/dev/vg00/lvol7 2048 1027 1013 50% /usr
/dev/vg00/lvol4 1024 6 1013 1% /tmp
/dev/vg00/lvol6 2048 1242 800 61% /opt
/dev/vg00/lvol5 400 162 237 41% /home
home/yd>

Again, you will see that we have oversized our /var and /tmp.

In fact, we use very little of our Internal disks space for keeping our Enterprise data. Our Internal disks are used for OS and OS-related applications only.

regards
Yogeeraj