[opensuse-autoinstall] Configuring multiple volume groups
Hi list, I have problems to create a working autoyast profile with 2 physical volumes and 2 volume groups. I am using SLES 10 and profile works for one VG. After adding another PV and a VG, yast complains, that it could not create "a logical volume of requested size" an no note has been logged to y2log. Size of disks is large enought available, of course. Here is the partitioning part of my profile: <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>auto</size> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_type>primary</partition_type> <size>auto</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>1GB</size> </partition> <partition> <lvm_group>system</lvm_group> <mount></mount> <partition_id config:type="integer">142</partition_id> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/system</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>usr</lv_name> <mount>/usr</mount> <size>2GB</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>var</lv_name> <mount>/var</mount> <size>2GB</size> <partition> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <lv_name>tmp</lv_name> <mount>/tmp</mount> <size>1GB</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>srv</lv_name> <mount>/srv</mount> <size>5GB</size> </partition> </partitions> <pesize>4M</pesize> <use>all</use> </drive> <drive> <device>/dev/cciss/c0d1</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <lvm_group>database</lvm_group> <mount></mount> <partition_id config:type="integer">142</partition_id> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/database</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiserfs</filesystem> <format config:type="boolean">true</format> <lv_name>oracle</lv_name> <mount>/var/opt/oracle</mount> <size>20GB</size> </partition> </partitions> <pesize>4M</pesize> <use>all</use> </drive> </partitioning> I also tried to use 2 seperate partitioning elements, but the later one overrides all. Also surprising was, that when using an empty partions list for the second volume group, a `pvscan' during installation shows, that both PVs are assigned to the same VG 'system'. Has anybody an idea? Regards Oliver -- Oliver Schweikert Software Development Horiba Europe Automation Division GmbH Zabergäustr. 3 73765 Neuhausen Tel: +49 - (0)7158-933-413 Fax: +49 - (0)7158-933-613 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
On Tuesday 24 April 2007 18:33, Oliver Schweikert wrote:
I have problems to create a working autoyast profile with 2 physical volumes and 2 volume groups. I am using SLES 10 and profile works for one VG. After adding another PV and a VG, yast complains, that it could not create "a logical volume of requested size" an no note has been logged to y2log. Size of disks is large enought available, of course.
Has anybody an idea?
try the driverupdate for SLES10: ftp://ftp.suse.com/pub/people/ug/autoyast I think you have hit a known bug -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Hi Uwe, thank you for the quick response. I will try the patch within the next few days. Is the fix included in SP1? Uwe Gansert wrote:
On Tuesday 24 April 2007 18:33, Oliver Schweikert wrote:
I have problems to create a working autoyast profile with 2 physical volumes and 2 volume groups. I am using SLES 10 and profile works for one VG. After adding another PV and a VG, yast complains, that it could not create "a logical volume of requested size" an no note has been logged to y2log. Size of disks is large enought available, of course.
Has anybody an idea?
try the driverupdate for SLES10: ftp://ftp.suse.com/pub/people/ug/autoyast
I think you have hit a known bug
-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
On Thursday 26 April 2007 11:12, Oliver Schweikert wrote:
thank you for the quick response. I will try the patch within the next few days. Is the fix included in SP1?
yes, that's fixed in SP1 -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Hi Uwe, after spending the last 2 days on the problem, here is my conslusion: the driverupdate file gets not integrated into the installation system, when it is a cpio archive. After creating a cramfs with the same contents, it works (updates are copied to /update/y2update). Creating multiple VG did also not work. I patched the file AutoinstLVM.ycp and now it seems to work. The patch file is attached to this email and i have not testet other partitioning profiles with it, yet, but maybe this patch will lead to a tidy solution. I must confess, not to understand much of the yast2 code, so i'm not sure, whether the changes are correct. Here is the partitioning snippet of my autoyast profile: <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>auto</size> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_type>primary</partition_type> <size>auto</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>1GB</size> </partition> <partition> <lvm_group>system</lvm_group> <mount></mount> <partition_id config:type="integer">142</partition_id> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/system</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>usr</lv_name> <mount>/usr</mount> <size>2GB</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>var</lv_name> <mount>/var</mount> <size>2GB</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>opt</lv_name> <mount>/opt</mount> <size>2GB</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>home</lv_name> <mount>/home</mount> <size>1GB</size> </partition> <partition> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <lv_name>tmp</lv_name> <mount>/tmp</mount> <size>1GB</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>srv</lv_name> <mount>/srv</mount> <size>1GB</size> </partition> </partitions> <pesize>4M</pesize> <use>all</use> </drive> <drive> <device>/dev/sdb</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <lvm_group>database</lvm_group> <mount></mount> <partition_id config:type="integer">142</partition_id> <partition_type>primary</partition_type> <size>9GB</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/database</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>oracle</lv_name> <mount>/var/opt/oracle</mount> <size>8GB</size> </partition> </partitions> <pesize>4M</pesize> <use>all</use> </drive> </partitioning> Regards Oliver Schweikert Software Development Horiba Europe Automation Division GmbH Zabergäustr. 3 73765 Neuhausen Tel: +49 - (0)7158-933-413 Fax: +49 - (0)7158-933-613 Email: osw@head.de
On Tuesday 12 June 2007 18:53, Oliver Schweikert wrote:
Here is the partitioning snippet of my autoyast profile:
you patched out the requirement for the specification of the partition_nr in the autoyast profile. There was a reason why I created that requirement but I can't remember the reason for that. :) If you specify the partition_nr, then the patch works without your modification (believe me, a lot of relieved customers second me on that ;) ). -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug now playing Colony 5 - Before I'll Give In -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Uwe Gansert wrote:
On Tuesday 12 June 2007 18:53, Oliver Schweikert wrote:
Here is the partitioning snippet of my autoyast profile:
you patched out the requirement for the specification of the partition_nr in the autoyast profile. There was a reason why I created that requirement but I can't remember the reason for that. :) If you specify the partition_nr, then the patch works without your modification (believe me, a lot of relieved customers second me on that ;) ).
You are right. After building all back to the original state, all works fine. Also I cannot reproduce the odd driverupdate behaviour, but i am sure, the line "dud: 0" at tty3 and the folder "/update" were missing after the update has been loaded...it's all mysterious to me. Never mind, sorry for the hoax! Maybe i'm getting slightly insane ;) Thank you for the help! Oliver -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (2)
-
Oliver Schweikert -
Uwe Gansert