"Cannot read device" on inactive volumes

Bug #1136494 reported by Lawren Quigley-Jones
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cryptsetup (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Release:
  Description: Ubuntu 10.04.4 LTS
  Release: 10.04
Version:
  cryptsetup:
  Installed: 2:1.1.0~rc2-1ubuntu13
  Candidate: 2:1.1.0~rc2-1ubuntu13
  Version table:
 *** 2:1.1.0~rc2-1ubuntu13 0
        500 http://apt/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

Scenario:
  I have an lvm2 snapshot of an encrypted volume.
  I mount the snapshot using cryptsetup.
  The available space is exceeded for the snapshot and is left "inactive" by the filesystem.
  At this point if I attempt to "luksClose" the crypt device the following error is issued:
     "Cannot read device /dev/mapper/crypt-snapshotvolume"
  I am unable to destroy the snapshot because it is in use.

Expected Behavior:
  I would expect luksClose to have a "force" option where it would close the device even though it cannot read it.

Bug:
  I am unable to destroy the snapshot without rebooting the system.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in cryptsetup (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.