Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
udisks2 loop-delete doesn't work for the loop device when the image deleted
Version-Release number of selected component (if applicable):
udisks2-2.7.3-6.el7.x86_64
udisks2-lvm2-2.7.3-6.el7.x86_64
libudisks2-2.7.3-6.el7.x86_64
RHEL-7.5 RC
How reproducible:
100%
Steps to Reproduce:
1. create and setup loop device with udisksctl
# udisksctl loop-setup -f /tmp/tfile_loop0
2. delete the image file of /tmp/tfile_loop0
# rm -rf /tmp/tfile_loop0
3. check the status of loop device
# losetup -l
NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE
/dev/loop0 0 0 1 0 /tmp/tfile_loop0 (deleted)
4. udisksctl delete the loop device
# udisksctl loop-delete --block-device /dev/loop0 ---> no output
5. check the loop device status
# losetup -l
NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE
/dev/loop0 0 0 1 0 /tmp/tfile_loop0 (deleted)
# udisksctl unmount --block-device /dev/loop0
Object /org/freedesktop/UDisks2/block_devices/loop0 is not a mountable filesystem.
Actual results:
* udisksctl doesn't work for device without image, moreover there is no output for the not work.
# udisksctl loop-delete --block-device /dev/loop0 ---> no output
# losetup -l
NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE
/dev/loop0 0 0 1 0 /tmp/tfile_loop0 (deleted)
Expected results:
* udisksctl works for the device without image or udisksctl can print some information and warning i.e "It is an invalid loop device, suggest to remove it with command ...."
Additional info:
Thanks Vojtech,
Let me test it again, let you know my result later.
Comment 6RHEL Program Management
2021-02-15 07:39:09 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.