Bug 1440766

Summary:	lvm2 - SIGINT leaves inconsistent metadata
Product:	Red Hat Enterprise Linux 7	Reporter:	Heinz Mauelshagen <heinzm>
Component:	lvm2	Assignee:	Heinz Mauelshagen <heinzm>
lvm2 sub component:	Default / Unclassified	QA Contact:	cluster-qe <cluster-qe>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	agk, cmarthal, heinzm, jbrassow, msnitzer, prajnoha, prockai, rbednar, zkabelac
Version:	7.4
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	lvm2-2.02.170-2.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 21:52:19 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 Heinz Mauelshagen 2017-04-10 12:41:00 UTC

Description of problem:
lvcreate or lvconvert can be interrupted via SIGINT leaving inconsistent metadata behind.  Same likely applies to other metadata updating commands.

Version-Release number of selected component (if applicable):
  LVM version:     2.02.167(2) (2016-11-05)
  Library version: 1.02.139-git (2017-03-28)
  Driver version:  4.35.0

How reproducible:
Almost always

Steps to Reproduce:
1. create/convert an e.g. RaidLV and send SIGIN (i.e. press ^C) immediately
2. vgs fails on inconsistent metadata
3.

Actual results:
vgs (and other commands) fail on inconsistent metadata

Expected results:
Consistent metadata either w/ or w/o the change via lvcreate/lvconvert

Additional info:

Comment 2 Heinz Mauelshagen 2017-04-10 15:33:42 UTC

There's an OBO bug in sigint_allow() causing the _oldmasked members to be set inproperly.

Comment 3 Heinz Mauelshagen 2017-04-10 16:17:14 UTC

Upstream commit 9a689fb8f0a6b1675a4e819f4837bf2e0269832f

Comment 4 Heinz Mauelshagen 2017-04-10 16:31:34 UTC

And upstream commit 4e21159a7f2c8d2806890b743866a0b9702e7532

Comment 7 errata-xmlrpc 2017-08-01 21:52:19 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://access.redhat.com/errata/RHBA-2017:2222