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.
Bug 1020304 - blkdeactivate loops when specific device name is used
Summary: blkdeactivate loops when specific device name is used
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: lvm2
Version: 6.6
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Peter Rajnoha
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-17 12:19 UTC by Nenad Peric
Modified: 2013-11-21 23:29 UTC (History)
10 users (show)

Fixed In Version: lvm2-2.02.100-7.el6
Doc Type: Bug Fix
Doc Text:
The blkdeactivate script iterates over the list of devices if they're given as an argument and it tries to unmount/deactivate them one by one. However, this iteration failed to proceed if any of the umount/deactivation was unsuccessful. As a result of this bug, the same device was tried again and again, causing an endless loop, never proceeding to the next device given. This has been fixed and if blkdeactivate fails to unmount/deactivate any of the devices given as an argument, the processing of the device is properly skipped and blkdeactivate proceeds with processing the next device given.
Clone Of:
Environment:
Last Closed: 2013-11-21 23:29:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1704 0 normal SHIPPED_LIVE lvm2 bug fix and enhancement update 2013-11-20 21:52:01 UTC

Description Nenad Peric 2013-10-17 12:19:10 UTC 
Description of problem:

If blkdeactivate is used with a specific device name which happens to be in use, it gets stuck in an infinite loop. 

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

lvm2-2.02.100-6.el6

How reproducible:

Everytime

Steps to Reproduce:

run blkdeactivate with a specific device which is currently being used:

blkdeactivate -u /dev/mirror_sanity/lvol0 
Deactivating block devices:
  [UMOUNT]: unmounting mirror_sanity-lvol0 (dm-2) mounted on /mnt/tests... skipping
  [UMOUNT]: unmounting mirror_sanity-lvol0 (dm-2) mounted on /mnt/tests... skipping
  [UMOUNT]: unmounting mirror_sanity-lvol0 (dm-2) mounted on /mnt/tests... skipping
  [UMOUNT]: unmounting mirror_sanity-lvol0 (dm-2) mounted on /mnt/tests... skipping
  [UMOUNT]: unmounting mirror_sanity-lvol0 (dm-2) mounted on /mnt/tests... skipping
  [UMOUNT]: unmounting mirror_sanity-lvol0 (dm-2) mounted on /mnt/tests... skipping
  [UMOUNT]: unmounting mirror_sanity-lvol0 (dm-2) mounted on /mnt/tests... skipping
  [UMOUNT]: unmounting mirror_sanity-lvol0 (dm-2) mounted on /mnt/tests... skipping
  [UMOUNT]: unmounting mirror_sanity-lvol0 (dm-2) mounted on /mnt/tests... skipping
.
.
.


Expected results:

Really SKIP after message said 'skipping' :)
Comment 3 Peter Rajnoha 2013-10-22 14:26:49 UTC 
Should be fixed with:

https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=b109bfc1ef7e20a72170a83dc9244c8b21ea658c
Comment 6 Nenad Peric 2013-10-24 09:07:34 UTC 
[root@virt-008 other1]# blkdeactivate -e -u /dev/vg/lvol0 
Deactivating block devices:
  [UMOUNT]: unmounting vg-lvol0 (dm-5) mounted on /mnt/other1... umount: /mnt/other1: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))
skipping
[root@virt-008 other1]# 


Verified with:

lvm2-2.02.100-7.el6.x86_64
Comment 7 errata-xmlrpc 2013-11-21 23:29:32 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1704.html
Note You need to log in before you can comment on or make changes to this bug.