You are not logged in.
The latest update of systemd to version 213-5 or 213-6 makes my snapshots of lvm crash.
When I try to remove the snapshot with "lvremove -f vg/lv1" I receive (most of the times) the following error
Unable to deactivate open vg-lv1-cow (254:7)
Failed to activate snapup.
Releasing activation in critical section.
libdevmapper exiting with 1 device(s) still suspended.
After this my systems hangs and I can only reboot it by manually shutting down my system.
I first tried downgrading lvm and my kernel, which did not solve it, so I expected an error in udev and tried downgrading systemd to version 212-3 which solved my problems. So the problems seems to be caused by systemd
I did not find anyone else with this problem, but maybe not many ppl use snapshots ????
Last edited by robin67 (2014-06-10 17:02:05)
Offline
I do and i have the same problem.
I got hit with it during my daily backup on my main machine. Suddenly my window manager froze but i could still move the mouse and switch to a TTY.
Since i couldn't kill any process acessing the home volume and the log indicated that this was the last volume that got snapshotted i saw the same error message.
I did a
dmsetup info /dev/mapper/system-home
and found it suspended. After a
dmsetup resume /dev/mapper/system-home
all processes returned, IO to the volume resumed and my window manager and all programms resumed as well.
After that the next lvremove on that snapshot worked, but left /dev/mapper/system-home-real behind. Which i removed by hand with:
dmsetup remove /dev/mapper/system-home-real
I found this thread discussing a similar bug in debian:
Offline
I opened a bug report for this, which has been solved by now.
Systemd version 213-9 (currently in testing) will solve this problem
Offline