From: Christian Lavoie <clavoie@bmed.mcgill.ca>
To: linux-kernel@vger.kernel.org
Subject: File resource leak in 2.2.19?
Date: Mon, 5 Nov 2001 17:09:36 -0500 [thread overview]
Message-ID: <20011105220945Z281381-17409+8838@vger.kernel.org> (raw)
I came to my work cluster only to find node4 dead. On the console,
"VFS: file-max limit 4096 reached"
Trying to login gave an error message about loading the shared libraries
required (since it couldn't get a file descriptor to load it, I guess)
The exact situation is an NFS share, hosted on a computer called 'node4';
files are accessed a couple of thousand times daily, read/write from a single
other machine thru user-space NFS daemon from Progeny 1.0, which then relays
X and/or VNC to a given Windows workstation. That's about the only access
pattern to the files.
It's possible that the said files will open from the node itself (Without
going thru NFS, but thru a strategically placed symlink), but I sincerely
doubt it happened.
Is there any known resource leak in 2.2.19 and up ('only' patched with MOSIX
0.98.0) that will exaust the available 'open file' resources?
Yours Truly,
Christian Lavoie
clavoie@bmed.mcgill.ca
reply other threads:[~2001-11-05 22:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20011105220945Z281381-17409+8838@vger.kernel.org \
--to=clavoie@bmed.mcgill.ca \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®