Package: dmeventd
Version: 2:1.02.90-2.2
Severity: important
Dear Maintainer,
While working a on ZFS root Debian installation, I've encoutered a
problem with dm-event.socket.
As it is loadeed too early, it create files in /var/run before the /var
volume being mounted.
Therefore /var remain unmounted and it's contents (like /var/lib)
unacessible.
Here is the opened files before the "zfs mount -a" command :
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd 1 root 27u FIFO 0,16 0t0 49154
/var/run/dmeventd-server
systemd 1 root 28u FIFO 0,16 0t0 49155
/var/run/dmeventd-client
As a workarround, I've added the following line in dm-event.socket
After=systemd-remount-fs.service
Regards
François.
-- System Information:
Debian Release: 8.4
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd
Versions of packages dmeventd depends on:
ii init-system-helpers 1.22
ii libc6 2.19-18+deb8u4
ii libdevmapper-event1.02.1 2:1.02.90-2.2
ii libdevmapper1.02.1 2:1.02.90-2.2
ii liblvm2cmd2.02 2.02.111-2.2
dmeventd recommends no packages.
dmeventd suggests no packages.
-- no debconf information