Am 11.05.2010 10:49, schrieb Lukas Grässlin:

I tested archlinux-2010.04.19-core-x86_64.iso and have some issues with installing with a lvm:

* It would be very very nice if I could say when creating a logical volume: "Take all the free space in the volumegroup" (aka -l100%FREE)

Good idea! I didn't run into this yet because I tend to only assign a fraction of the available space during installation (i.e. on a 300GB volume, I use 10GB for system, 4GB for swap and 20GB for /home, let the rest unused).

* If I type a value greater than the free space in the vg the installer says it encountered errors. Would be better if it is checked, if the value exceeds the free space.

Good idea. Also didn't run into this for the same reasons.

At the current state I wouldn't use the Installers capability to create a LVM because it's a bit glitchy.

Always worked for me so far.

The same is true of the capability of creating dm-crypt volumes. Till now I was not able to set up a working scenario with LVM atop of dm-crypt. The Installers also fails with some errors. (I don't have more information about this yet because it's a bit longer ago. I will retest it)

I installed a system using AIF from git in February or March I think (the current CDs contain a newer AIF version). I had no trouble setting this up back then.

On 05/11/2010 04:49 AM, Lukas Grässlin wrote:

* It would be very very nice if I could say when creating a logical volume: "Take all the free space in the volumegroup" (aka -l100%FREE)

Yes, I've thought about the 100%FREE before, so +1

At the current state I wouldn't use the Installers capability to create a LVM because it's a bit glitchy.

The same is true of the capability of creating dm-crypt volumes. Till now I was not able to set up a working scenario with LVM atop of dm-crypt. The Installers also fails with some errors. (I don't have more information about this yet because it's a bit longer ago. I will retest it)

I've done a number of lvm2/luks setups. On the luks end, are you setting your keysize too low? For aes-xts-plain, the key size can only be 256 or 512, so if you set it to 128 you'll have a problem. The other thing I've wound up doing every time for it to work is to make sure I use the same exact name for the encrypted disk and the vg. So typically I call the dm-crypt parition "vg0" so it mounts to /dev/mapper/vg0 Matt

Am 11.05.2010 13:13, schrieb Matthew Monaco:

I've done a number of lvm2/luks setups. On the luks end, are you setting your keysize too low? For aes-xts-plain, the key size can only be 256 or 512, so if you set it to 128 you'll have a problem.

aes-xts-plain also allows 384.

The other thing I've wound up doing every time for it to work is to make sure I use the same exact name for the encrypted disk and the vg. So typically I call the dm-crypt parition "vg0" so it mounts to /dev/mapper/vg0

That isn't necessary. The name of the dm-crypt volume doesn't matter at all actually. I always call it "lvm" or "pv".

On Thu, 13 May 2010 14:44:34 +0200 Lukas Grässlin wrote:

Hi there again :)

I forgot another thing: If I have two disks and I want to use the secons disk completely as PV I normally don't need a partition on that disk, i just do:

pvcreate /dev/sdb and that's it.

In AIF I have to create a partition that fits the complet disk size.

Of course, thats no problem. I just wanted to told this to you ;)

no you don't. afaik, aif lets you do what you want. Dieter

On Thu, 13 May 2010 15:24:55 +0200 Lukas Grässlin wrote:

On 05/13/2010 02:51 PM, Dieter Plaetinck wrote:

...

On Thu, 13 May 2010 14:44:34 +0200 Lukas Grässlin wrote:

...

Hi there again :)

I forgot another thing: If I have two disks and I want to use the secons disk completely as PV I normally don't need a partition on that disk, i just do:

pvcreate /dev/sdb and that's it.

In AIF I have to create a partition that fits the complet disk size.

Of course, thats no problem. I just wanted to told this to you ;)

no you don't. afaik, aif lets you do what you want.

Dieter

Mh sorry, my fault. With the latest iso I also can use entire disks as PV. Alright ;)

Another thing I just yet encountered is, that when creating a lv if I enter a greater value than the vg size is (the thing from my first post in this thread) of course the creating fails. AIF tells me "Error creating...etc". So far, so good, but if I klick "Enter" it tries again and again to create the lv and fails of course. I'm in a loop and only can exit the installer.

use the rollback feature. Dieter

On 05/13/2010 03:28 PM, Lukas Grässlin wrote:

...

...

Another thing I just yet encountered is, that when creating a lv if I enter a greater value than the vg size is (the thing from my first post in this thread) of course the creating fails. AIF tells me "Error creating...etc". So far, so good, but if I klick "Enter" it tries again and again to create the lv and fails of course. I'm in a loop and only can exit the installer.

use the rollback feature. Dieter

How may I use this when I can't escape from this loop. It always tells me "Error creating lv..." and after confirming that it tells me again.

Mh, I found out that the problems does not seem to be size size but that I already had a volumegroup on the disk. So it cannot initialize the pv because it was in another volumegroup. -- Lukas Grässlin GnuPG-Key: http://lg.ath.cx/lukasgraesslin@gmx.de.asc

On 05/13/2010 03:33 PM, Dieter Plaetinck wrote:

On Thu, 13 May 2010 15:28:43 +0200 Lukas Grässlin wrote:

...

...

...

Another thing I just yet encountered is, that when creating a lv if I enter a greater value than the vg size is (the thing from my first post in this thread) of course the creating fails. AIF tells me "Error creating...etc". So far, so good, but if I klick "Enter" it tries again and again to create the lv and fails of course. I'm in a loop and only can exit the installer.

use the rollback feature. Dieter

How may I use this when I can't escape from this loop. It always tells me "Error creating lv..." and after confirming that it tells me again.

well if you can't, that's a bug and it should be reported. Dieter

Obviously it's not completely AIFs fault, cause I already had an volumegroup there. (I totally forgot this). Maybe it's possible for AIF to check if there are alredy volumegroups or something or is this not useful? I don't know if that will be a good idea or not. If yes I may create a bug report/feature request. -- Lukas Grässlin GnuPG-Key: http://lg.ath.cx/lukasgraesslin@gmx.de.asc

On 05/13/2010 03:40 PM, Dieter Plaetinck wrote:

On Thu, 13 May 2010 15:37:34 +0200 Lukas Grässlin wrote:

...

On 05/13/2010 03:33 PM, Dieter Plaetinck wrote:

...

On Thu, 13 May 2010 15:28:43 +0200 Lukas Grässlin wrote:

...

...

...

Another thing I just yet encountered is, that when creating a lv if I enter a greater value than the vg size is (the thing from my first post in this thread) of course the creating fails. AIF tells me "Error creating...etc". So far, so good, but if I klick "Enter" it tries again and again to create the lv and fails of course. I'm in a loop and only can exit the installer.

use the rollback feature. Dieter

How may I use this when I can't escape from this loop. It always tells me "Error creating lv..." and after confirming that it tells me again.

well if you can't, that's a bug and it should be reported. Dieter

Obviously it's not completely AIFs fault, cause I already had an volumegroup there. (I totally forgot this).

Maybe it's possible for AIF to check if there are alredy volumegroups or something or is this not useful? I don't know if that will be a good idea or not. If yes I may create a bug report/feature request.

you're the user, you know you have a VG, just don't add another one with the same name. (BTW the rollback feature will make aif undo all changes it did itself, ie it will remove VG's it made, but not the one you already had.) if you want this feature, someone will need to contribute a patch.

Dieter

Mh, I think you're right. It was just a thought. Btw: I retestet setting up a LVM with two PVs and I did not get it work: http://bugs.archlinux.org/task/19448 With only on PV it works. -- Lukas Grässlin GnuPG-Key: http://lg.ath.cx/lukasgraesslin@gmx.de.asc