I also try to keep /var (even /var/log), /home, and /tmp on separate file systems. It reduces the chances of phone calls at 3AM!
Additionally I provide a 20cyl. /config disk which I maintain from CMS. On startup, boot.local reads from /config to customize the Linux instance on the fly. Ray Mrohs -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of RPN01 Sent: Tuesday, April 08, 2008 1:36 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: What is a good generic disk layout? We're using the following layout: Allocate the following disks to the Linux guest: * 124 cylinders minimum as device num 391, used as /boot * 10016 cylinders minimum as device num 392, used as vg_system. * 10016 cylinders minimum as device num 393, used as vg_local * ?? cylinders as device numbers 394+, used as vg_app, vg_dbXXXX, etc. as required by app During the Linux install, allocate the disk as follows: * /dev/dasda1 (391) as /boot * /dev/dasdb1 (392) as LVM vg_system o / - 2.0 gb o /var - 2.5 gb o /tmp - 500 mb o swap - 1 gb * /dev/dasdc1 (393) as LVM vg_local o /home - 2 gb o /opt - 5.4 gb This provides us with a minimal /boot outside of LVM, isolates /var and /tmp from the root file system, and places /home and /opt on its own disk. This leaves us with a disk usage after install somewhat like the following: [EMAIL PROTECTED]:~> df Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/vg_system-lv_root 2890692 2074908 668944 76% / udev 509860 104 509756 1% /dev /dev/dasda1 87076 16544 66040 21% /boot /dev/mapper/vg_local-lv_home 2064208 95864 1863488 5% /home /dev/mapper/vg_local-lv_opt 4954828 595096 4108036 13% /opt /dev/mapper/vg_system-lv_tmp 495944 110616 359728 24% /tmp /dev/mapper/vg_system-lv_var 2580272 216860 2232340 9% /var [EMAIL PROTECTED]:~> Hope this helps... -- Robert P. Nix Mayo Foundation .~. RO-OE-5-55 200 First Street SW /V\ 507-284-0844 Rochester, MN 55905 /( )\ ----- ^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 4/8/08 10:31 AM, "Adam Thornton" <[EMAIL PROTECTED]> wrote: > On Apr 8, 2008, at 9:45 AM, Romanowski, John (OFT) wrote: > >> can't you make partition1 dasda1 /boot and partition2 dasda2 the PV >> for >> LVM? > > Sub-partitioning DASD on zSeries is really not a very good idea. > > If you're running under VM, you've already GOT virtualized disk. > > Make /dev/dasda a small /boot parition (so, only give it 80 cylinders > or something) and make /dev/dasdb a bigger volume which you can make > into an LVM PV if you want to. > > Adam ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
