Summary: | sys-fs/cryptsetup: manually opened devices are not closed, causing sys-fs/lvm2 "read failed" on shutdown | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | proxy-maint |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | screen shot |
Description
Toralf Förster
2009-10-26 20:37:13 UTC
Created attachment 208351 [details]
screen shot
important to reproduce it : use an external USB drive, plug it in after login as root, plug out it before reboot if, right before you reboot, you shutdown the luks, does the problem go away? I'm thinking it's due to dm-crypt mappings not being removed, and then when device-mapper tries to finally stop, those mappings still exist. (In reply to comment #3) > if, right before you reboot, you shutdown the luks, does the problem go away? yes, luksClose removes thuis issue This is not an LVM problem then. The dm-crypt scripts should probably be closing ALL dm-crypt devices, not just those registered in /etc/conf.d/dm-crypt. vapier: ACK on closing all dm-crypt devices? vapier: reping yes, that makes sense |