Bug 892039

Summary:	upon shutdown/reboot system hangs with lvm errors - having a volume on top of a iscsi device
Product:	Red Hat Enterprise Linux 6	Reporter:	lejeczek <peljasz>
Component:	lvm2	Assignee:	LVM and device-mapper development team <lvm-team>
Status:	CLOSED DUPLICATE	QA Contact:	Cluster QE <mspqa-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.3	CC:	agk, dwysocha, heinzm, jbrassow, msnitzer, prajnoha, prockai, thornber, zkabelac
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-01-07 08:20:24 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 lejeczek 2013-01-04 22:42:06 UTC

Description of problem:

seems that iscsi daemon turns down before lvm2-monitor does

boot if fine but shutdown/reboot is not, needs to be helped with ctrl-alt-del for it hangs spiting errors about vg/lv in question.


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

lvm2-libs-2.02.95-10.el6.x86_64
lvm2-2.02.95-10.el6.x86_64
iscsi-initiator-utils-6.2.0.872-41.el6.x86_64
initscripts-9.03.31-2.el6.x86_64


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 Peter Rajnoha 2013-01-07 08:20:24 UTC

There's a new "blkdeactivate" command called from a new "blk-availability" init service we've added lately in lvm2-2.02.98-1.el6. This service cleans up all device-mapper-based devices (including LVM) before iscsi and fcoe is down. It's included in RHEL6.4.

Please, try the latest lvm2 build version >= 2.02.98-1 and if the problem still persists, reopen this bug. Thanks.

There's also an existing bug tracking this change: bug #800801 (also original bug #672530).

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

Comment 3 lejeczek 2013-01-07 10:13:38 UTC

where could a src.rpm be held of?
thanks!

Comment 4 lejeczek 2013-01-07 12:14:32 UTC

is it going to be backported to 6.3?

Comment 5 Peter Rajnoha 2013-01-07 15:37:16 UTC

(In reply to comment #3)
> where could a src.rpm be held of?
> thanks!

Actually, the 6.4 is not fully completed yet. It's still under testing. However, if you want to give it a try to see if it resolves your problem, I can provide srpm, but without any warranty for now! I'll be including a few more patches this week, so I can send you one later this week...

(In reply to comment #4)
> is it going to be backported to 6.3?

There's no plan yet to include this in 6.3.z. This change also depends on other changes (in util-linux/lsblk) that I'm afraid are not going to be backported as it's quite a big change in functionality and we want to avoid any possible regressions that might be introduced by such a backport. So only RHEL 6.4+.

Comment 6 lejeczek 2013-01-07 15:54:00 UTC

I've grabbed lvm2-2.02.98-3.el6.x86_64 along with all deps, seems fine for now, but will take a closer look in the next few days.

please let us know when it's patched and more ready.
thanks