| Summary: | double /dev/mapper output in cryptsetup status command | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Alexander Todorov <atodorov> |
| Component: | cryptsetup-luks | Assignee: | Ondrej Kozina <okozina> |
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 6.1 | CC: | agk, coughlan, jstodola, mbroz, prajnoha, prockai, zkabelac |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | cryptsetup-luks-1.2.0-7.el6 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-06-20 14:16:27 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 756082 | ||
|
Description
Alexander Todorov
2011-10-17 11:38:04 UTC
Hm. But status really takes just mapped name for argument, not a path. This should not work at all :) Fixed in cryptsetup-luks-1.2.0-7.el6. # rpm -q cryptsetup-luks cryptsetup-luks-1.2.0-7.el6.x86_64 # cryptsetup status /dev/mapper/luks-14e91c9c-3159-444c-bf4d-f7af8814728c /dev/mapper/luks-14e91c9c-3159-444c-bf4d-f7af8814728c is active and is in use. type: LUKS1 cipher: aes-xts-plain64 keysize: 512 bits device: /dev/vda2 offset: 4096 sectors size: 15747072 sectors mode: read/write # cryptsetup status luks-14e91c9c-3159-444c-bf4d-f7af8814728c /dev/mapper/luks-14e91c9c-3159-444c-bf4d-f7af8814728c is active and is in use. type: LUKS1 cipher: aes-xts-plain64 keysize: 512 bits device: /dev/vda2 offset: 4096 sectors size: 15747072 sectors mode: read/write VERIFIED. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0886.html |