dmeventd: Child exited with code 1

buggyazyn · 10-09-2012, 12:59 AM

Good day:

I just upgraded from 13.37 to 14.0 and when i run:

# lvcreate -s -L10G -n snap /dev/vg0/archive
Child exited with code 1
Unable to start dmeventd.
Child exited with code 1
Unable to start dmeventd.
vg0-snap: event registration failed: No such process
vg0/snapshot0: snapshot segment monitoring function failed.
Logical volume "snap" created

The errors disappear if /run/lvm directory is created. It seems a bug in Slackware 14.0.

xflow7 · 10-24-2012, 05:59 AM

Hi,

I've just come across the same behavior, Slack64 14.0

Dave

GazL · 10-24-2012, 07:36 AM

Yep I think you're right.

lvm2 was configured with

Code:

 --with-default-locking-dir=/run/lock/lvm \
  --with-default-run-dir=/run/lvm \

Both of those probably ought to be created by the initrd and/or early rc.S. Might be worth dropping Pat a note.

jtsn · 10-25-2012, 11:26 PM

Stumbled over issue too. So LVM snapshots are currently broken in Slackware 14?

gitarrmongot · 06-27-2013, 11:06 AM

Sorry to bring up an old post but, I just noticed I have the same problem. Does anyone know if this has been addressed in current? Also is there a particular reason for using /run as opposed to /var/run?

catkin · 10-14-2013, 03:59 AM

Quote:

Originally Posted by GazL

Yep I think you're right.

lvm2 was configured with

Code:

 --with-default-locking-dir=/run/lock/lvm \
  --with-default-run-dir=/run/lvm \

Both of those probably ought to be created by the initrd and/or early rc.S. Might be worth dropping Pat a note.

Thanks GazL

Why did you suggest creating those directories during boot? On my Slackware64 14.0, /run is on the / file system, it is not tmpfs. OTOH the /run/lvm directory disappears (/run/lock/lvm remains) ...