On Wed, Sep 19, 2007 at 11:27:33PM +0800, Hans wrote:
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.
I feel difficult to believe it is file descriptors that cause you
problems. That debug message is only annoying and i don't see why it is
there at all.
what i see from the scarce info you posted is:
LVM[8796]: 2007/09/10_14:55:26 INFO: Deactivating volume group
vg0_sites
LVM[8796]: 2007/09/10_14:55:26 INFO: File descriptor 3 left open
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
so lvm is asked to deactivate vg vg0_sites and it does it, this appears
to be normal.
maybe _reading_ the log file of which you graciously let us know only
two lines will give you more hints about what is going on.
also if you are asking for help, detailing your configuration will
usually result in people being able to understand what you are talking
about.
finally if you suspect an issue with lvm you could configure debug
options under the "log" section of /etc/lvm/lvm.conf and analyze the
resulting logs.
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
