Bug 1419909 - device-mapper: remove ioctl on backup failed: Device or resource busy - luksClose vs. mkfs.btrfs
Summary: device-mapper: remove ioctl on backup failed: Device or resource busy - luksC...
Alias: None
Product: Fedora
Classification: Fedora
Component: device-mapper
Version: 25
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2017-02-07 11:39 UTC by Georg Sauthoff
Modified: 2017-12-12 10:27 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-12 10:27:43 UTC
Type: Bug

Attachments (Terms of Use)

Description Georg Sauthoff 2017-02-07 11:39:44 UTC
Description of problem:
The `cryptsetup luksClose $somedevice` writes the following errors when it is called directly after a `mkfs.btrfs $somedevice` command.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. cryptsetup luksFormat /dev/disk/by-id/usb-$usbtestdrive && cryptsetup luksOpen /dev/disk/by-id/usb-$usbtestdrive backup && mkfs.btrfs /dev/mapper/backup  && sync && cryptsetup luksClose backup

Actual results:
device-mapper: remove ioctl on backup failed: Device or resource busy
kernel: device-mapper: ioctl: unable to remove open device backup

$ echo $?

Expected results:

no such error messages

and/or if there is really a serious error: echo $? != 0

Additional info:

I can work around this via adding a sleep between the mkfs and luksClose call, i.e.:

$ cryptsetup luksFormat /dev/disk/by-id/usb-$usbtestdrive && cryptsetup luksOpen /dev/disk/by-id/usb-$usbtestdrive backup && mkfs.btrfs /dev/mapper/backup  && sync && sleep 1 && cryptsetup luksClose backup

Comment 1 Fedora End Of Life 2017-11-16 19:35:07 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2017-12-12 10:27:43 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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