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.

Bug 1201733

Summary:	Add After=iscsi-shutdown.service to blk-availability.service for proper shutdown before iscsi sessions are logged out
Product:	Red Hat Enterprise Linux 7	Reporter:	Peter Rajnoha <prajnoha>
Component:	lvm2	Assignee:	Peter Rajnoha <prajnoha>
lvm2 sub component:	Other	QA Contact:	cluster-qe <cluster-qe>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	agk, cmarthal, heinzm, jbrassow, msnitzer, nperic, prajnoha, prockai, tnishimura, zkabelac
Version:	7.1	Keywords:	Triaged
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	lvm2-2.02.125-1.el7	Doc Type:	Bug Fix
Doc Text:	Before, the blk-availability.service was not ordered with respect to iSCSI services properly. The blk-availability service is responsible for handling shutdown of dm-based block devices (including LVM and multipath devices) and such improper ordering could have caused the iSCSI devices to be detached on system shutdown sequence before dm-based devices were deactivated, ending up with possible IO errors then. The blk-availability.service systemd unit is now properly ordered so that it's always executed before iscsi-shutdown.service responsible for detaching iSCSI devices.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-19 12:46:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Peter Rajnoha 2015-03-13 11:32:19 UTC

RHEL uses a separate iscsi-shutdown.service for iscsi session logout in contrast to upstream's iscsi.service. Add After=iscsi-shutdown.service to blk-availability.service that is responsible for deactivating dm-based devices. This should be done before any iscsi devices underneath are logged out.

(I expect the iscsi-shutdown will eventually get upstream as well.)

The patch is here:

https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=05f23e77634b2ed3d7861511c07ed73a3bb6d096

Comment 1 Peter Rajnoha 2015-03-13 14:01:05 UTC

See also related bug #1201030.

Comment 3 Corey Marthaler 2015-10-19 17:11:55 UTC

Marking verified (SanityOnly) based on results listed in bug 1201030.


3.10.0-325.el7.x86_64
lvm2-2.02.130-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
lvm2-libs-2.02.130-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
lvm2-cluster-2.02.130-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
device-mapper-1.02.107-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
device-mapper-libs-1.02.107-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
device-mapper-event-1.02.107-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
device-mapper-event-libs-1.02.107-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
device-mapper-persistent-data-0.5.5-1.el7    BUILT: Thu Aug 13 09:58:10 CDT 2015
cmirror-2.02.130-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
sanlock-3.2.4-1.el7    BUILT: Fri Jun 19 12:48:49 CDT 2015
sanlock-lib-3.2.4-1.el7    BUILT: Fri Jun 19 12:48:49 CDT 2015
lvm2-lockd-2.02.130-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015



[root@host-082 ~]# systemctl enable blk-availability.service
Created symlink from /etc/systemd/system/sysinit.target.wants/blk-availability.service to /usr/lib/systemd/system/blk-availability.service.
[root@host-082 ~]# systemctl status blk-availability.service
â blk-availability.service - Availability of block devices
   Loaded: loaded (/usr/lib/systemd/system/blk-availability.service; enabled; vendor preset: disabled)
   Active: active (exited) since Mon 2015-10-19 16:08:57 CDT; 4h 7min left
 Main PID: 1108 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/blk-availability.service

Oct 19 16:08:57 host-082.virt.lab.msp.redhat.com systemd[1]: Starting Availability of block devices...
Oct 19 16:08:57 host-082.virt.lab.msp.redhat.com systemd[1]: Started Availability of block devices.

[root@host-082 ~]# systemctl stop blk-availability.service
[root@host-082 ~]# systemctl status blk-availability.service
â blk-availability.service - Availability of block devices
   Loaded: loaded (/usr/lib/systemd/system/blk-availability.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Mon 2015-10-19 12:09:46 CDT; 6s ago
  Process: 2913 ExecStop=/usr/sbin/blkdeactivate -u -l wholevg (code=exited, status=0/SUCCESS)
 Main PID: 1108 (code=exited, status=0/SUCCESS)

Oct 19 16:08:57 host-082.virt.lab.msp.redhat.com systemd[1]: Starting Availability of block devices...
Oct 19 16:08:57 host-082.virt.lab.msp.redhat.com systemd[1]: Started Availability of block devices.
Oct 19 12:03:48 host-082.virt.lab.msp.redhat.com systemd[1]: Started Availability of block devices.
Oct 19 12:09:46 host-082.virt.lab.msp.redhat.com systemd[1]: Stopping Availability of block devices...
Oct 19 12:09:46 host-082.virt.lab.msp.redhat.com blkdeactivate[2913]: Deactivating block devices:
Oct 19 12:09:46 host-082.virt.lab.msp.redhat.com blkdeactivate[2913]: [SKIP]: unmount of rhel_host--082-swap (dm-1) mounted on [SWAP]
Oct 19 12:09:46 host-082.virt.lab.msp.redhat.com blkdeactivate[2913]: [SKIP]: unmount of rhel_host--082-root (dm-0) mounted on /
Oct 19 12:09:46 host-082.virt.lab.msp.redhat.com blkdeactivate[2913]: [LVM]: deactivating Volume Group cache_sanity... done
Oct 19 12:09:46 host-082.virt.lab.msp.redhat.com systemd[1]: Stopped Availability of block devices.

Comment 4 errata-xmlrpc 2015-11-19 12:46:16 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.

https://rhn.redhat.com/errata/RHBA-2015-2147.html