Hi Jochen, Am 01.10.2015 um 00:04 schrieb Michael Biebl: > Control: reassign -1 cryptsetup > > Am 10.07.2015 um 07:23 schrieb Jochen Sprickerhof: >> I've debugged a little more and actually it's not only enough to do a >> swapoff -a, but you need also a cryptsetup close /dev/mapper/swap0 >> (sorry for forgetting it initiallly). >> The shutdown hangs in the do_close() of >> /lib/cryptsetup/cryptdisks.functions (line 556), where cryptsetup remove >> is call. Adding a -v --debug gives: >> >> [..] >> # Initialising device-mapper backend library. >> # dm table swap0 OFW [16384[ (*1) >> # Trying to open and read device /dev/sda5. >> # Deactivating volume swap0. >> # dm status swap0 OF [16384] (*1) >> # Udev cookie 0xd4d9dac (semid 65536) created >> # Udev cookie 0xd4d9dac (semid 65536) incremented to 1 >> # Udev cookie 0xd4d9dac (semid 65536) incremented to 2 >> # Udev cookie 0xd4d9dac (semid 65536) assigned to REMOVE task(2) with flags >> (0x0) >> # dm remove swap0 OF [16384] (*1) >> # swap0: Stacking NODE_DEL [verify_udev] >> # Udev cookie 0xd4d9dac (semid 65536) decrementing to 1 >> # Udev cookie 0xd4d9dac (semid 65536) waiting for zero > > this looks like a cryptsetup/device-mapper issue.
Could you try to replace 'cryptsetup remove' by 'dmsetup --check close' and see whether the shutdown process still hangs? Cheers jonas
signature.asc
Description: OpenPGP digital signature
