| 1 |
systemd-204 |
| 2 |
lvm2-2.0.2.99-r2 |
| 3 |
|
| 4 |
(lvm2 patched as mentioned in |
| 5 |
|
| 6 |
https://bugs.gentoo.org/show_bug.cgi?id=480066 |
| 7 |
|
| 8 |
this should only matter for activation) |
| 9 |
|
| 10 |
- |
| 11 |
|
| 12 |
See what happens here: |
| 13 |
|
| 14 |
# lvcreate -n mlp-tmpl -L 11G VG02 |
| 15 |
/dev/VG02/mlp-tmpl: not found: device not cleared |
| 16 |
Aborting. Failed to wipe start of new LV. |
| 17 |
device-mapper: remove ioctl on failed: Das Gerät oder die Ressource |
| 18 |
ist belegt |
| 19 |
semid 163841: semop failed for cookie 0xd4d92b7: incorrect semaphore state |
| 20 |
Failed to set a proper state for notification semaphore identified by |
| 21 |
cookie value 223187639 (0xd4d92b7) to initialize waiting for incoming |
| 22 |
notifications. |
| 23 |
|
| 24 |
|
| 25 |
# lvcreate -n mlp-tmpl -L 11G -Zn VG02 |
| 26 |
WARNING: "mlp-tmpl" not zeroed |
| 27 |
Logical volume "mlp-tmpl" created |
| 28 |
semid 196609: semop failed for cookie 0xd4d74cd: incorrect semaphore state |
| 29 |
Failed to set a proper state for notification semaphore identified by |
| 30 |
cookie value 223179981 (0xd4d74cd) to initialize waiting for incoming |
| 31 |
notifications. |
| 32 |
|
| 33 |
|
| 34 |
https://bugzilla.redhat.com/show_bug.cgi?id=727925 |
| 35 |
|
| 36 |
talks of udev_sync=1 ... checked that, is there ... |
| 37 |
|
| 38 |
CONFIG_NET_NS=y (whatever that is ... do I need it?) |
| 39 |
|
| 40 |
... |
| 41 |
|
| 42 |
Does anyone know what to do? I wanted to ask here before I file a bug at |
| 43 |
bgo ... |
| 44 |
|
| 45 |
Would be nice to solve this before I set up my shiny new KVM host where |
| 46 |
I heavily want to use LVM-snapshots for backups. Sure, I could also stay |
| 47 |
with openrc, correct! |
| 48 |
|
| 49 |
(didn't mention: had that semaphore stuff on my main workstation as |
| 50 |
well, only when booting via systemd) |
| 51 |
|
| 52 |
Thanks, Stefan |
Archives