From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx1.redhat.com (mx1.redhat.com [172.16.48.31]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l8JFQxA2014899 for ; Wed, 19 Sep 2007 11:26:59 -0400 Received: from postman.formosahost.com (postman.formosahost.com [203.190.4.19]) by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l8JFQloh013015 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 19 Sep 2007 11:26:51 -0400 Received: from localhost (localhost [127.0.0.1]) by postman.formosahost.com (Postfix) with ESMTP id 9870D8A264 for ; Wed, 19 Sep 2007 23:23:17 +0800 (CST) Received: from postman.formosahost.com ([127.0.0.1]) by localhost (postman.formosahost.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 2XCd8F6p3gXV for ; Wed, 19 Sep 2007 23:23:15 +0800 (CST) Received: from [192.168.0.6] (61-56-145-65-adsl-tpe.STATIC.so-net.net.tw [61.56.145.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by postman.formosahost.com (Postfix) with ESMTP id D13998A263 for ; Wed, 19 Sep 2007 23:23:14 +0800 (CST) Message-ID: <46F13FE5.6010905@ezpear.com> Date: Wed, 19 Sep 2007 23:27:33 +0800 From: Hans MIME-Version: 1.0 Subject: Re: [linux-lvm] lvm HA problem with file descriptor left open References: <46E4F110.6040003@ezpear.com> <20070917213319.GV18444@agk.fab.redhat.com> In-Reply-To: <20070917213319.GV18444@agk.fab.redhat.com> Content-Type: multipart/alternative; boundary="------------060506060201070208030401" Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: To: LVM general discussion and development This is a multi-part message in MIME format. --------------060506060201070208030401 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Alasdair G Kergon wrote: > On Mon, Sep 10, 2007 at 03:24:00PM +0800, hans wrote: > >> File descriptor 5 left open File descriptor 6 left open File descriptor >> 7 left open File descriptor 8 left open File descriptor 9 left open File >> descriptor 10 left open File descriptor 11 left open File descriptor 12 >> left open 0 logical volume(s) in volume group "vg0_sites" now active >> Is it possible to force LVM >> to close descriptors? >> > > Those are only harmless warnings - LVM2 does close the file descriptors. > It is only fatal under some selinux configurations. > > Alasdair > Thanks for answer. But I don't think it is harmless. When my server shutdown , and my backup is up high availability doesn't work. DRBD doesn't start because of this error. After I manual set up drbd active, I can not see files created on main machine . After I again start main machine and start DRBD I can see all files. I think it is problem with descriptors which cause errors in my HA. I heard that I can use CLVM, but I don't know how it is compatible with LVM. Regards, Hans --------------060506060201070208030401 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Alasdair G Kergon wrote:
On Mon, Sep 10, 2007 at 03:24:00PM +0800, hans wrote:
  
File descriptor 5 left open File descriptor 6 left open File descriptor
7 left open File descriptor 8 left open File descriptor 9 left open File
descriptor 10 left open File descriptor 11 left open File descriptor 12
left open 0 logical volume(s) in volume group "vg0_sites" now active
Is it possible to force LVM
to close descriptors?
    
 
Those are only harmless warnings - LVM2 does close the file descriptors.
It is only fatal under some selinux configurations.

Alasdair
  

Thanks for answer.
But I don't think it is harmless. When my server shutdown , and my backup is up high availability doesn't work.
DRBD  doesn't start because of this error.
After I manual set up drbd active, I can not see files created on main machine .
After I again start main machine and start DRBD I can see all files.
I think it is problem with descriptors which cause errors in my HA.
I heard that I can use CLVM, but I don't know how it is compatible with LVM.

Regards,
Hans
--------------060506060201070208030401--