Yes, it's a valid point. Reason is we want to be able just to move disks between servers when upgrading for example. Especially for /opt This layout is for RHEL7 which has a slightly different disk setup, so here the whole os is more or less in dev 200. It's also made to make it simpler to implement read-only root for placing it in shared memory segment. For RHEL6 and our prev SLES we had it more like your way :-) To avoid extra admin we have a script that increase an lvm mountpoint, taking care of everything. It starts with a VM rexx that allocates dasd disk, pick first free devnr in a serie and then sends an smsg to the server telling it diskdevno, mountpoint and email for result-info. We have udev rules for smsg so the script is triggered directly, fixing everything and mail us about the result. A real time-saver !
BR /Tore ________________________________________________ Tore Agblad zOpen Teamleader IT Services Volvo Group Headquarters Corporate Process & IT Dept. DE94230 Assar Gabrielssons väg 9 SE-405 08, Gothenburg Sweden Soft Phone: +46 313086198 Telephone: +46-31-3233569 E-mail: tore.agb...@volvo.com http://www.volvo.com/volvoit/global/en-gb/ -----Original Message----- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: den 24 juni 2015 4:13 To: LINUX-390@VM.MARIST.EDU Subject: Re: Custom Layout >>> On 6/24/2015 at 09:01 AM, Agblad Tore <tore.agb...@volvo.com> wrote: > I did it this way: > First our wanted setup. > > DeviceNr Mountpoint Cyls Type > 200 / 2000 xfs native > 201 /boot 500 xfs native > 202 VDISK swap 128000 block swap > 203 VDISK swap 128000 block swap > 204 swap 2000 swap > 205 if more swap needed > 250 /usr 5000 xfs lvm usrvg-usr > 251 when adding disks to this lvm > 260 /opt 3000 xfs lvm optvg-opt > 261 when adding disks to this lvm > 270 /var 4000 xfs lvm varvg-var > 271 when adding disks to this lvm > 280 /tmp 1500 xfs lvm tmpvg-tmp > 281 when adding disks to this lvm > 290 /home 500 xfs lvm homevg-home > 291 when adding disks to this lvm It would seem to me that having a separate volume group for each file system sort of defeats the purpose of using LVM in the first place. While I would recommend that user data be in a different VG from the OS, this approach looks to increase the amount of effort for both thez/VM systems programmer and the Linux system administrator. Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
