Hi,
We are hitting this too now after years using lvremove in
late_command. Also while Squeeze was testing we were using this
without any problem.
Anyway problem seems to be that the late_command is invoked chrooted
in /target.
While calling lvremove from the debian-installer rootfs works, calling
lvremove in the chroot immediately hangs waiting for some lock.
CTRL+C'ing it leads to the message
CTRL-c detected: giving up waiting for lock
/var/lock/lvm/V_$vgname: flock failed: Interrupted system call
Can't get lock for $vgname
Skipping volume group $vgname
/proc and /sys are mounted.
Maybe because device-mapper isn't started yet or so...?
Andreas
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive:
http://lists.debian.org/[email protected]
