Cryptsetup behaving differently at login

[bonnevie]

I've been using full disk encryption with cryptsetup in my LL2.8 (Lenovo) for over a year now.
So far no problem, but I noticed a change in booth process since a recent cryptsetup update. Everytime I log in with a correct pw, this is what I get:

Code: [Select]

Please unlock disk sda5_crypt(*****myfakepw*****)
Reading all physical volumes - this could take a while
Found volume group "Linux-vg" using metadate type lvm2
2 logical volumes in volume group "linux-vg" now active
cryptsetup: unknown fstype, bad password or option?
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device-mapper: remove ioct1 on sda5_crypt failed: device or resource busy
device sda5_crypt still in use
cryptsetup: sda5_crypt set up successfully
Overall, the result is still that the disk ends up decrypted.
But I don't understand what the system is telling me (sda5 still in use? how so?), and why it changed from a simple login to this new full-verbose message. Anyone noticed this?