From: Jonathan E Brassow <jbrassow@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] file descriptor 3 left open
Date: Tue, 24 Jan 2006 16:48:54 -0600 [thread overview]
Message-ID: <a748b5eda735d5fda0e77b266ea94402@redhat.com> (raw)
In-Reply-To: <CF88E297901EB040B49935FE71B99A2D01F49E12@CTTRBEXVS01.oxhp.com>
[-- Attachment #1: Type: text/plain, Size: 1976 bytes --]
IIRC, these are merely informative messages saying that, "Hey, the
person who called me forgot to close some of their file descriptors,
like they were suppose to. But don't worry, I'll close them for you."
That would have been too long though, so I think they chose a more
cryptic message.
As far as your kernel installation problem, I'm not sure what's wrong
there...
You could 'rpm -q kernel' (or rpm -qa | grep kernel) to see if it is
installed. If it is, you could 'rpm -ql kernel-<the version> | grep
boot' to see if the image was correctly installed...
brassow
On Jan 24, 2006, at 3:55 PM, Kapadia, Nayan U. wrote:
> I keep seeing "file descriptor 3 left open" at boot after the initrd
> is loaded. The systems boots to the 2.6.9-22.0.1 kernel and works
> fine. I have ran fsck against all filesystems however the error
> messages still appears. I noticed that when I run system-config-lvm
> these errors are more predominant.
>
> File descriptor 13 left open
> File descriptor 3 left open
> File descriptor 4 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
> File descriptor 13 left open
> File descriptor 3 left open
> File descriptor 4 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
> File descriptor 13 left open
>
> I recently installed the new kernel 2.6.9-22.0.2 but the system does
> not find kernel at boot. I think the file descriptor messages are a
> symptom to some greater problem. Please help.
>
> thank you!
>
> Nayan
>
>
> _______________________________________________
> 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/
[-- Attachment #2: Type: text/enriched, Size: 3391 bytes --]
IIRC, these are merely informative messages saying that, "Hey, the
person who called me forgot to close some of their file descriptors,
like they were suppose to. But don't worry, I'll close them for you."
That would have been too long though, so I think they chose a more
cryptic message.
As far as your kernel installation problem, I'm not sure what's wrong
there...
You could 'rpm -q kernel' (or rpm -qa | grep kernel) to see if it is
installed. If it is, you could 'rpm -ql kernel-<<the version> | grep
boot' to see if the image was correctly installed...
brassow
On Jan 24, 2006, at 3:55 PM, Kapadia, Nayan U. wrote:
<excerpt><fontfamily><param>Arial</param><smaller>I keep seeing "file
descriptor 3 left open" at boot after the initrd is loaded. The
systems boots to the 2.6.9-22.0.1 kernel and works fine. I have ran
fsck against all filesystems however the error messages still
appears. I noticed that when I run system-config-lvm these errors are
more predominant. </smaller></fontfamily>
<fontfamily><param>Arial</param><smaller>File descriptor 13 left open</smaller></fontfamily>
<fontfamily><param>Arial</param><smaller>File descriptor 3 left open</smaller></fontfamily>
<fontfamily><param>Arial</param><smaller>File descriptor 4 left open</smaller></fontfamily>
<fontfamily><param>Arial</param><smaller>File descriptor 8 left open</smaller></fontfamily>
<fontfamily><param>Arial</param><smaller>File descriptor 9 left open</smaller></fontfamily>
<fontfamily><param>Arial</param><smaller>File descriptor 10 left open</smaller></fontfamily>
<fontfamily><param>Arial</param><smaller>File descriptor 11 left open</smaller></fontfamily>
<fontfamily><param>Arial</param><smaller>File descriptor 12 left open</smaller></fontfamily>
<fontfamily><param>Arial</param><smaller>File descriptor 13 left open</smaller></fontfamily>
<fontfamily><param>Arial</param><smaller>File descriptor 3 left open</smaller></fontfamily>
<fontfamily><param>Arial</param><smaller>File descriptor 4 left open</smaller></fontfamily>
<fontfamily><param>Arial</param><smaller>File descriptor 8 left open</smaller></fontfamily>
<fontfamily><param>Arial</param><smaller>File descriptor 9 left open</smaller></fontfamily>
<fontfamily><param>Arial</param><smaller>File descriptor 10 left open</smaller></fontfamily>
<fontfamily><param>Arial</param><smaller>File descriptor 11 left open</smaller></fontfamily>
<fontfamily><param>Arial</param><smaller>File descriptor 12 left open</smaller></fontfamily>
<fontfamily><param>Arial</param><smaller>File descriptor 13 left open</smaller></fontfamily>
<fontfamily><param>Arial</param><smaller>I recently installed the new
kernel 2.6.9-22.0.2 but the system does not find kernel at boot. I
think the file descriptor messages are a symptom to some greater
problem. Please help.</smaller></fontfamily>
<fontfamily><param>Arial</param><smaller>thank you!</smaller></fontfamily>
<fontfamily><param>Arial</param><smaller>Nayan</smaller></fontfamily>
<fontfamily><param>Arial</param><smaller> </smaller></fontfamily>
_______________________________________________
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/</excerpt>
next prev parent reply other threads:[~2006-01-24 22:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 21:55 [linux-lvm] file descriptor 3 left open Kapadia, Nayan U.
2006-01-24 22:48 ` Jonathan E Brassow [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-24 23:07 Kapadia, Nayan U.
2006-01-24 23:22 ` Jonathan E Brassow
2006-01-25 14:11 Kapadia, Nayan U.
2006-01-25 14:26 ` Alasdair G Kergon
2006-01-25 14:33 Kapadia, Nayan U.
2006-01-25 14:35 ` Alasdair G Kergon
2006-01-25 14:51 Kapadia, Nayan U.
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=a748b5eda735d5fda0e77b266ea94402@redhat.com \
--to=jbrassow@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).