* Volkmar Glauche <glauche@uke.uni-hamburg.de> [Jun 10. 2002 21:04]:
Hi,
I have the following partitioning configuration on 2 SCSI disks:
(deleted)
and lvm
<lvm config:type="list"> <lvm_group> <lvm_name>HomeVol</lvm_name> <pesize>4M</pesize> <logical_volumes config:type="list">
<lv>
<lv_name>LHomeVol</lv_name> <lv_size>29200mb</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/export/home</lv_mount>
</lv>
</logical_volumes> </lvm_group> </lvm>
You need an <lv> tag here as you also can define multiple (a list) of logical volumes.
i.e., what I want to have is a logical volume spanning 2 physical volumes. What yast2 does is something else (unfortunately log files are deleted):
Please try the update package from ftp://ftp.suse.com/pub/people/nashif/autoyast2
- 1st it partitions /dev/sda - 2nd it creates a volume group HomeVol consisting of the lvm partion on disk /dev/sda - 3rd it partitions /dev/sdb - 4th it cannot create another volume group HomeVol with the partition on /dev/sdb, because a volume group with this label does already exist Afterwards I added the corresponding configuration manually and encountered another problem: The size of the volume group was calculated by yast to be 27.3G (in the screen where volumes are assigned to volume groups), but on the next screen I was offered a maximum file system size of 27.9G for formatting. This did not work out, for obvious reasons...
Hmmm, I can't reproduce. BTW, you have t PVs of 14gb and you create an LV with 29,2 GB! How should this work? Or am I missing something?
In addition, neither mount points are created for the swap partitions nor the swap partitions initialised.
This might be the cause of a parse error in the lvm resource (no lv tag).
In addition, I would like to be able to configure mount points that are not assigned to devices at install time (like tmpfs, usb storage devices), but I can not find a way to configure them outside the <partition> sections.
Configure in what way! Aren;t those filesystems automatically added to fstab?
Also, on this disk configuration, lilo did not install successfully in automated mode. The initrd was created and contained the aic7xxx module for the SCSI controller, but the root device entry in /etc/lilo.conf pointed to "nil" instead of /dev/sda6.
hopfully all these problems are removed with the update package... Regards, Anas -- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada