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 1703902 - LVM "stop" jobs timeout delays shutdown
Summary: LVM "stop" jobs timeout delays shutdown
Keywords:
Status: CLOSED DUPLICATE of bug 1704165
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lvm2
Version: 7.7
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: LVM and device-mapper development team
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-29 04:03 UTC by Yanqiu Zhang
Modified: 2019-04-29 11:52 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-29 11:52:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
lvm2-shutdown.log (8.86 KB, application/gzip)
2019-04-29 04:03 UTC, Yanqiu Zhang
no flags Details

Description Yanqiu Zhang 2019-04-29 04:03:46 UTC
Created attachment 1559740 [details]
lvm2-shutdown.log

Description of problem:
When shutdown, this job timeout then delays shutdown time

Version-Release number of selected component (if applicable):
lvm2-2.02.184-2.el7.x86_64
kernel-3.10.0-1040.el7.x86_64
device-mapper-1.02.156-2.el7.x86_64


How reproducible:
100%

Steps to Reproduce:
tested on guest:
1. start a normal guest
[root@localhost ~]# lsblk
NAME          MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda           252:0    0  10G  0 disk 
├─vda1        252:1    0   1G  0 part /boot
└─vda2        252:2    0   9G  0 part 
  ├─rhel-root 253:0    0   8G  0 lvm  /
  └─rhel-swap 253:1    0   1G  0 lvm  [SWAP]
[root@localhost ~]# dmsetup table
rhel-swap: 0 2097152 linear 252:2 2048
rhel-root: 0 16769024 linear 252:2 2099200
[root@localhost ~]# dmsetup status
rhel-swap: 0 2097152 linear 
rhel-root: 0 16769024 linear 
[root@localhost ~]# dmsetup ls --tree
rhel-swap (253:1)
 └─ (252:2)
rhel-root (253:0)
 └─ (252:2)
#  dmsetup info -c
Name             Maj Min Stat Open Targ Event  UUID                                                                
rhel-swap        253   1 L--w    2    1      0 LVM-zmPokncbxNcPsWeo2c88diicfGfuiWMcbQgMG0cVZ7UcC3Dodz6YhxURMg2ipok4
rhel-root        253   0 L--w    1    1      0 LVM-zmPokncbxNcPsWeo2c88diicfGfuiWMcDgEkTYavclVhLHYEWzdSiQ4SO4LjzCU1

2.[root@localhost ~]# shutdown -h now

3.Check guest shutdown progress by virt-manager or virsh console, a lvm2 job is being waited, and it delays the shutdown time:
...
[***   ] A stop job is running for LVM2 metadata daemon (51s / 1min 33s)
...


Actual results:
As step3.

Expected results:
the lvms job should finish quickly then do not delay shutdown

Additional info:
Systemd debugging log from serial console will be put in attachment.
(by booting with "systemd.log_level=debug systemd.log_target=console console=ttyS0,115200 console=tty0")

Comment 6 Zdenek Kabelac 2019-04-29 11:52:00 UTC

*** This bug has been marked as a duplicate of bug 1704165 ***


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