[arch-general] Big changes to LVM2 in testing
I discovered some new awesomeness in LVM2 (okay, not THAT new, but still, so far unknown to me). In our lvm2 package, I enabled lvmetad - this is a metadata caching daemon that reacts to events from udev. I completely reorganized our systemd and mkinitcpio lvm integration: * lvm.service and lvm-on-crypt.service are gone. * Once you install lvm2, lvmetad.socket and dmeventd.socket are always active in systemd. * If you need LVM monitoring, you need to enable lvm-monitoring.service (recommended if you use LVM, even if you don't know if you need monitoring). I didn't enable this by default because it would always start lvmetad.service. * LVM is fully hotplugged via udev. You don't need to activate anything, LVM volumes will just work. LVM no longer requires systemd-udev-settle.service and all the race conditions should be gone. * LVM in mkinitcpio is also fully hotplugged, lvmwait= is now a no-op. However, LVM in mkinitcpio now requires the udev hook. This requires that the use_lvmetad = 1 option is set in /etc/lvm/lvm.conf - this is now the default, but a .pacnew must be merged if it exists. You can restrict the hotplugging of the volume groups with the auto_activation_volume_list option in lvm.conf. If you uncomment that, only the listed volumes will be enabled. This is commented out by default. WARNING: If you have any incomplete or clustered volume groups, none of this will work yet! However, I doubt any Arch user uses that.
Thomas Bächler <thomas@archlinux.org> on Thu, 2012/11/01 02:05:
I discovered some new awesomeness in LVM2 (okay, not THAT new, but still, so far unknown to me).
Just to be sure and as "in testing" can lead to some confusion... This has been enabled in 2.02.98-2? -- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Chris get my mail address: */=0;b=c[a++];) putchar(b-1/(/* gcc -o sig sig.c && ./sig */b/42*2-3)*42);}
Am 01.11.2012 15:22, schrieb Christian Hesse:
Thomas Bächler <thomas@archlinux.org> on Thu, 2012/11/01 02:05:
I discovered some new awesomeness in LVM2 (okay, not THAT new, but still, so far unknown to me).
Just to be sure and as "in testing" can lead to some confusion... This has been enabled in 2.02.98-2?
Yes, correct.
Thomas Bächler <thomas@archlinux.org> on Thu, 2012/11/01 15:34:
Am 01.11.2012 15:22, schrieb Christian Hesse:
Thomas Bächler <thomas@archlinux.org> on Thu, 2012/11/01 02:05:
I discovered some new awesomeness in LVM2 (okay, not THAT new, but still, so far unknown to me).
Just to be sure and as "in testing" can lead to some confusion... This has been enabled in 2.02.98-2?
Yes, correct.
Now that we have bigger changes to the package... How about moving everything to /usr/ and getting rid of the complicated configure call? I have not tested myself yet, but it should work. I think this is a big step forward for the usr-move in Arch. -- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Chris get my mail address: */=0;b=c[a++];) putchar(b-1/(/* gcc -o sig sig.c && ./sig */b/42*2-3)*42);}
Am 02.11.2012 10:59, schrieb Christian Hesse:
Thomas Bächler <thomas@archlinux.org> on Thu, 2012/11/01 15:34:
Am 01.11.2012 15:22, schrieb Christian Hesse:
Thomas Bächler <thomas@archlinux.org> on Thu, 2012/11/01 02:05:
I discovered some new awesomeness in LVM2 (okay, not THAT new, but still, so far unknown to me).
Just to be sure and as "in testing" can lead to some confusion... This has been enabled in 2.02.98-2?
Yes, correct.
Now that we have bigger changes to the package... How about moving everything to /usr/ and getting rid of the complicated configure call?
I have not tested myself yet, but it should work. I think this is a big step forward for the usr-move in Arch.
Sounds like a good idea. Sadly, the configure will not become much simpler.
Thomas Bächler <thomas@archlinux.org> on Fri, 2012/11/02 11:31:
Am 02.11.2012 10:59, schrieb Christian Hesse:
Thomas Bächler <thomas@archlinux.org> on Thu, 2012/11/01 15:34:
Am 01.11.2012 15:22, schrieb Christian Hesse:
Thomas Bächler <thomas@archlinux.org> on Thu, 2012/11/01 02:05:
I discovered some new awesomeness in LVM2 (okay, not THAT new, but still, so far unknown to me).
Just to be sure and as "in testing" can lead to some confusion... This has been enabled in 2.02.98-2?
Yes, correct.
Now that we have bigger changes to the package... How about moving everything to /usr/ and getting rid of the complicated configure call?
I have not tested myself yet, but it should work. I think this is a big step forward for the usr-move in Arch.
Sounds like a good idea. Sadly, the configure will not become much simpler.
You are right, it does not... However 2.02.98-3 works for me like a charm. Thanks! -- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Chris get my mail address: */=0;b=c[a++];) putchar(b-1/(/* gcc -o sig sig.c && ./sig */b/42*2-3)*42);}
On Fri, Nov 02, 2012 at 10:59:41AM +0100, Christian Hesse wrote:
Thomas Bächler <thomas@archlinux.org> on Thu, 2012/11/01 15:34:
Am 01.11.2012 15:22, schrieb Christian Hesse:
Thomas Bächler <thomas@archlinux.org> on Thu, 2012/11/01 02:05:
I discovered some new awesomeness in LVM2 (okay, not THAT new, but still, so far unknown to me).
Just to be sure and as "in testing" can lead to some confusion... This has been enabled in 2.02.98-2?
Yes, correct.
Now that we have bigger changes to the package... How about moving everything to /usr/ and getting rid of the complicated configure call?
pacman 4.1 is a blocker for moving ahead with the /usr merge. It hugely improves the conflict checking when directories become symlinks.
Am 02.11.2012 13:43, schrieb Dave Reisner:
On Fri, Nov 02, 2012 at 10:59:41AM +0100, Christian Hesse wrote:
Thomas Bächler <thomas@archlinux.org> on Thu, 2012/11/01 15:34:
Am 01.11.2012 15:22, schrieb Christian Hesse:
Thomas Bächler <thomas@archlinux.org> on Thu, 2012/11/01 02:05:
I discovered some new awesomeness in LVM2 (okay, not THAT new, but still, so far unknown to me).
Just to be sure and as "in testing" can lead to some confusion... This has been enabled in 2.02.98-2?
Yes, correct.
Now that we have bigger changes to the package... How about moving everything to /usr/ and getting rid of the complicated configure call?
pacman 4.1 is a blocker for moving ahead with the /usr merge. It hugely improves the conflict checking when directories become symlinks.
This doesn't stop us from gradually moving binaries to /usr/bin if their paths aren't hardcoded anywhere.
participants (3)
-
Christian Hesse
-
Dave Reisner
-
Thomas Bächler