systemd-204 lvm2-2.0.2.99-r2
(lvm2 patched as mentioned in https://bugs.gentoo.org/show_bug.cgi?id=480066 this should only matter for activation) - See what happens here: # lvcreate -n mlp-tmpl -L 11G VG02 /dev/VG02/mlp-tmpl: not found: device not cleared Aborting. Failed to wipe start of new LV. device-mapper: remove ioctl on failed: Das Gerät oder die Ressource ist belegt semid 163841: semop failed for cookie 0xd4d92b7: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223187639 (0xd4d92b7) to initialize waiting for incoming notifications. # lvcreate -n mlp-tmpl -L 11G -Zn VG02 WARNING: "mlp-tmpl" not zeroed Logical volume "mlp-tmpl" created semid 196609: semop failed for cookie 0xd4d74cd: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223179981 (0xd4d74cd) to initialize waiting for incoming notifications. https://bugzilla.redhat.com/show_bug.cgi?id=727925 talks of udev_sync=1 ... checked that, is there ... CONFIG_NET_NS=y (whatever that is ... do I need it?) ... Does anyone know what to do? I wanted to ask here before I file a bug at bgo ... Would be nice to solve this before I set up my shiny new KVM host where I heavily want to use LVM-snapshots for backups. Sure, I could also stay with openrc, correct! (didn't mention: had that semaphore stuff on my main workstation as well, only when booting via systemd) Thanks, Stefan
