Stephan, comments below...
Stephan Esterhuizen wrote:
Hello, I'm running SI 3.5.3 and am having some trouble with the <image>.master and autoinstallscript.conf files: ------ Setup: ------ /dev/md0 : /boot RAID1 (sda1 sdb1) /dev/md1 : swap RAID0 (sda2 sdb2)
Just a little advice... doing RAID0 on a swap device is meaningless, or anyway, not so efficient, since the kernel already stripes in multiple devices, if you specify the opportune priority in the mount options...
For details: http://www.tldp.org/HOWTO/Software-RAID-HOWTO-2.html#ss2.3
/dev/md2 : / RAID0 (sda3 sdb3) /dev/md3 : LVM RAID0 (sda4 sdb4) 1) The autoinstallscript.conf file has this line: <part num="4" size="*" p_type="primary" p_name="-" flags="raid" /> Which should really read: <part num="4" size="*" p_type="primary" p_name="-" flags="raid,lvm" lvm_group="vg" /> For some reason it didn't detect that /dev/md3 should be RAID *and* LVM... I added the above line to see where it would take me: (I believe these lines are generated based on the partition type flag, obviously I can only set either raidautodetect or lvm, not both and that is probably why it incorrectly set these flag?).
There is no reason to specify both raid and lvm flags, since the LVM is created *on top* of the soft-RAID volume and not at the same logical layer. So you need only the "raid" flag to define a RAID volume, then with a pvcreate /dev/md0 you can enable the RAID volume to be part of a LVM group.
Anyways, so later on it appears that: 2) <image>.master script - mkraid for /dev/md3 never executed - mkswap for /dev/md1 never executed - LVM tried to create volume group on /dev/sda4, NOT /dev/md3 - apparently it was unaware that LVM sits on a raid partition (and not /dev/sda4 - which is part of the md3 raid partition). Perhaps my 'flags="raid,lvm"' hack was a bad idea?
The 3.5.3 version doesn't support LVM over RAID volumes. I've done some hacks to support this feature in the developer trunk available via svn, and I'm currently using this feature without problem, but it works only from the image server side (I mean at the moment the si_prepareclient is not able to generate an opportune autoinstallscript.conf with LVM over RAID volumes, so, for now, you need to edit the autoinstallscript.conf on the image server, before running the si_mkautoinstallscript).
Follow this thread for details: http://sourceforge.net/mailarchive/forum.php?thread_id=8013968&forum_id=8921
Regards, -Andrea -- Andrea Righi System Management Group - CINECA - http://www.cineca.it Via Magnanelli 6/3 40033 Casalecchio di Reno (BO) - Italy tel: +39 051 61 71 908 (office) gpg --keyserver keyserver.veridis.com --recv-keys 77CEF397 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
