Thanks for the reply, never knew about dmsetup before.
Here's the output:
# dmsetup info satadisks_vg-backup_lv
Name: satadisks_vg-backup_lv
State: ACTIVE
Read Ahead: 1024
Tables present: LIVE
Open count: 1
Event number: 0
Major, minor: 252, 3
Number of targets: 1
UUID: LVM-<REMOVED>
Since the device shouldn't be open by anything (I've even rebooted the box to ensure no stale locks) how do I go about finding out what has it locked, and how do I safely remove that lock?
thanks
Paul
On Fri, Aug 28, 2009 at 2:44 PM, Milan Broz <mbroz@xxxxxxxxxx> wrote:
Paul Bradley wrote:
>
> Following a power failure and reboot luksOpen is failing for an
> encrypted device:
>
> ~$ sudo cryptsetup luksOpen /dev/satadisks_vg/backup_lv cryptbackup
> Command failed: Can not access device
> open("/dev/satadisks_vg/backup_lv",This means that device exclusive open failed.
> O_RDONLY|O_EXCL|O_SYNC|O_DIRECT|O_LARGEFILE) = -1 EBUSY (Device or
> resource busy)
Check "dmsetup info" for open count for this device - should be 0.
Milan
_______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
