On Fri, Jan 11, 2008 at 03:31:18PM -0500, Wayman Smith wrote:
I have modified my autoyast to a simpler partitioning scheme. This seems to work. However, eventually I will need to add support for a more advanced partitioning scheme with multiple drives. Do you suggest using the Autoinstallation tool, or editing the bare xml file? I have attached the modified autoinst.xml file. Below is the partitioning scheme I would like to implement.
You can already do more advanced partitioning for multiple drives (and differing numbers/types of drives) by creating the partitioning info in separate files and using the existing rules framework to read in the matching situation automatically.
sda1
- /boot 100M
- /swap 2GB
- / 30GB
- LVM max
sda2
- LVM max
volgrp1
- logical volume 1 max
I'm doing some LVM stuff (on one disk) already. I'm using only some of the disk for the OS and leaving the rest available for xen instances.
I attached the file for doing this if you're curious about how to get LVM going in autoyast.
If you have a situation with sda and sdb ( assume you actually meant that above vs sda1 and sda2) you could use something based on my attached file with 2 sections that create the initial LVM devices, one with: <device>/dev/sda</device> and named something like: <lvm_group>diskone</lvm_group> and then second section exactly the same except for the /boot partition and the following differences: <device>/dev/sdb</device> and named something like: <lvm_group>disktwo</lvm_group>
Then you can make your partitions on: <device>/dev/diskone</device> and <device>/dev/disktwo</device>
You'll note from my example too, that you don't need to keep the OS partitions outside of the LVM group.. only /boot needs to be outside it so that grub (or lilo or any bootloader you like) can read the kernel and initrd. Even swap works find inside lvm.