All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans <hans@ezpear.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvm HA problem with  file descriptor left open
Date: Wed, 19 Sep 2007 23:27:33 +0800	[thread overview]
Message-ID: <46F13FE5.6010905@ezpear.com> (raw)
In-Reply-To: <20070917213319.GV18444@agk.fab.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 1524 bytes --]

  reply	other threads:[~2007-09-19 15:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-10  7:24 [linux-lvm] lvm HA problem with file descriptor left open hans
2007-09-17 21:33 ` Alasdair G Kergon
2007-09-19 15:27   ` Hans [this message]
2007-09-20  6:57     ` Luca Berra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46F13FE5.6010905@ezpear.com \
    --to=hans@ezpear.com \
    --cc=linux-lvm@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.