Bug 673039 - device-mapper: ioctl: unable to remove open device temporary-cryptsetup-xxxx
Summary: device-mapper: ioctl: unable to remove open device temporary-cryptsetup-xxxx
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: cryptsetup-luks
Version: 14
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: LVM and device-mapper development team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-27 06:43 UTC by japa-fi
Modified: 2011-01-31 09:43 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-31 09:43:45 UTC
Type: ---


Attachments (Terms of Use)

Description japa-fi 2011-01-27 06:43:14 UTC
Description of problem:
When opening luks device an error message is printed out. 
Actual operation seems to be successful.

Version-Release number of selected component (if applicable):
Name        : cryptsetup-luks
Arch        : x86_64
Version     : 1.1.3
Release     : 1.fc14


Name        : cryptsetup-luks-libs
Arch        : x86_64
Version     : 1.1.3
Release     : 1.fc14
Size        : 86 k

How reproducible:
Every time

Steps to Reproduce:
1. cryptsetup luksOpen /dev/... name
2. 
3.
  
Actual results:
device-mapper: ioctl: unable to remove open device temporary-cryptsetup-2930

Expected results:
No error message

Additional info:

Comment 1 Milan Broz 2011-01-27 09:12:45 UTC
How do you open luks device? From command line or through GUI?

if from command line, try add --debug and post output.
(try it several times, it should print which process opens that device).

This is not bug in cryptsetup but in some udev subsytem which wrongly opens internal cryptsetup device.

Comment 2 japa-fi 2011-01-31 09:43:45 UTC
Fortunately or unfortunately, depending on the point of view, I haven't been able to reproduce this issue since my system restart which was done after I had submitted the ticket.

Either the issue has been fixed by some recent updates
or it was something strange in my workstation and cleared by restart.

Either way - > Worksforme. Sorry for wasting your time.


Note You need to log in before you can comment on or make changes to this bug.