Bug 432994

Summary:	lvm.sh 'File descriptor X left open' messages
Product:	Red Hat Enterprise Linux 5	Reporter:	Lon Hohberger <lhh>
Component:	rgmanager	Assignee:	Jonathan Earl Brassow <jbrassow>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	5.2	CC:	cluster-maint, edamato
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-01-27 18:07:56 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	431713
Bug Blocks:

Description Lon Hohberger 2008-02-15 16:54:37 UTC

Description of problem:

When running rg_test, you get strange messages from lvm.sh:

[root@grant-03 ~]# rg_test test /etc/cluster/cluster.conf stop service halvm
Running in test mode.
Stopping halvm...
<debug>  stop: Could not match /dev/GRANT/ha2 with a real device
<debug>  fs (isMounted): Could not match /dev/GRANT/ha2 with a real device
<info>   /dev/GRANT/ha2 is not mounted
<debug>  stop: Could not match /dev/GRANT/ha1 with a real device
<debug>  fs (isMounted): Could not match /dev/GRANT/ha1 with a real device
<info>   /dev/GRANT/ha1 is not mounted
File descriptor 4 left open
File descriptor 4 left open
  volume_list=["VolGroup00", "@grant-03"]
File descriptor 4 left open
  0 logical volume(s) in volume group "GRANT" now active
File descriptor 4 left open
File descriptor 4 left open
File descriptor 4 left open
Stop of halvm complete

Version-Release number of selected component (if applicable): rgmanager-2.0.36-1.el5

How reproducible: 100%

I do not think this is critical at all.  I saw it while trying to track down
another issue fore Corey.

Comment 1 Jonathan Earl Brassow 2008-02-15 17:03:39 UTC

volume_list=["VolGroup00", "@grant-03"]  should not be printed.  There is an
update waiting for 5.3 that changes this section of code...  This issue may go
away when that one (bug #431713) is fixed.

Comment 2 Lon Hohberger 2010-01-27 18:07:56 UTC


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