Bug 532606
Summary: | After 12beta update, LUKS strangeness, inability to unmount | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ryan Rix <ry> |
Component: | lvm2 | Assignee: | Milan Broz <mbroz> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 12 | CC: | agk, bmarzins, bmr, dwysocha, heinzm, lvm-team, mbroz, msnitzer, prajnoha, prockai, pvrabec |
Target Milestone: | --- | Keywords: | Reopened, Triaged |
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-06-22 21:48:59 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ryan Rix
2009-11-03 00:26:40 UTC
This looks really terryfiyng, but there is no risk of losing data - the IO error are on temporary cryptsetup device, which is wrongly accessed by other application, cryptsetup intentionally remaps it to error devoce to prevek possible keyslot leaks. BTW for the LUKS device is in use probably because LVM voulmes are activated on it (you need to deactivate them first.) (Please can you retest it with new updates? See the duplicate bug.) *** This bug has been marked as a duplicate of bug 528909 *** Thanks; I know no data is at risk, it's just pretty annoying how it hangs up plymouth and is impossible to delete. I'm playing with lvchange right now, but somehow it's in use to the point where I can't even lvchange it... I'm confused by the matter in general. I odn't have enough experience with LVM to debug it :( I'll update and then take a look at 528909 The bug that this one has been marked duplicate of is on a component I don't even have installed. I'm going to open this back up, as a result. This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping I added flags instructing udev rules to not scan temporary devices in cryptsetup, also it now tries to used udev if avaliable, so in next release these messages ("buffer i/o error" when scanning) should never appear again. (It requires new udev + device-mapper, so it is in next Fedora release only.) no idea how it is with s-c-lvm and umount, if you have still that problem, please report separate bug, thanks. |