Hi, I have the following partitioning configuration on 2 SCSI disks: <partitioning config:type="list"> <drive> <device>/dev/sda</device> <use>all</use> <partitions config:type="list"> <partition> <filesystem config:type="symbol">swap</filesystem> <filesystem_id config:type="integer">130</filesystem_id> <format config:type="boolean">true</format> <mount/> <size>768M</size> <type>Linux swap</type> </partition> .... some other partitions <partition> <lvm_group>HomeVol</lvm_group> <size>14000M</size> <filesystem_id config:type="integer">142</filesystem_id> <type>Linux LVM</type> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <filesystem_id config:type="integer">131</filesystem_id> <format config:type="boolean">true</format> <mount>/usr</mount> <size>max</size> <type>Linux native</type> </partition> </partitions> </drive> <drive> <device>/dev/sdb</device> <use>all</use> <partitions config:type="list"> ... some other partitions <partition> <filesystem_id config:type="integer">142</filesystem_id> <type>Linux LVM</type> <lvm_group>HomeVol</lvm_group> <size>14000M</size> </partition> </partitions> </drive> and lvm <lvm config:type="list"> <lvm_group> <lvm_name>HomeVol</lvm_name> <pesize>4M</pesize> <logical_volumes config:type="list"> <lv_name>LHomeVol</lv_name> <lv_size>29200mb</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/export/home</lv_mount> </logical_volumes> </lvm_group> </lvm> 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): - 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... In addition, neither mount points are created for the swap partitions nor the swap partitions initialised. 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. 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. Yours, Volkmar -- Volkmar Glauche E-Mail glauche@uke.uni-hamburg.de Department of Neurology WWW http://www.uni-jena.de/~nvg/ UKE Hamburg Phone 49(0)40-42803-5781 Martinistr. 52 Fax 49(0)40-42803-5086 20246 Hamburg
* 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
On Tue, 11 Jun 2002, Anas Nashif wrote:
You need an <lv> tag here as you also can define multiple (a list) of logical volumes.
Thanks, I missed that...
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
Thank you, I will have a go on it!
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?
The numbers were just what yast2 calculated for me.
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?
Not by default. As an example, I would like to have an mountpoint tmpfs /tmp tmpfs defaults,mode=0777 for the /tmp file system. Also I have got an USB zip drive that may be used with all workstations in the department. But when I install them with autoyast, the zip drive will not be auto-detected because it will not be present at that time. So I need to add a line /dev/sdXX /media/zip auto noauto,users manually (and create the mount point). In addition, I would like to be able to set the default options for any removable media to "...,users,..." instead of "...,user,..." Up to now I have used a post-script that does these things, but this could interfere with changes made by yast2. Yours, Volkmar -- Volkmar Glauche Department of Neurology E-Mail glauche@uke.uni-hamburg.de UKE Hamburg WWW http://glauche.home.pages.de/ Martinistr. 52 Phone 49(0)40-42803-5781 20246 Hamburg Fax 49(0)40-42803-9955
* Volkmar Glauche <glauche@uke.uni-hamburg.de> [Jun 11. 2002 08:27]:
Not by default. As an example, I would like to have an mountpoint
tmpfs /tmp tmpfs defaults,mode=0777
for the /tmp file system. Also I have got an USB zip drive that may be used with all workstations in the department. But when I install them with autoyast, the zip drive will not be auto-detected because it will not be present at that time. So I need to add a line
/dev/sdXX /media/zip auto noauto,users
manually (and create the mount point). In addition, I would like to be able to set the default options for any removable media to "...,users,..." instead of "...,user,..." Up to now I have used a post-script that does these things, but this could interfere with changes made by yast2.
Ok, I got your point and I think it is a MUST feature for 8.1, so we will be working on that. Anas -- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
participants (2)
-
Anas Nashif -
Volkmar Glauche