* File resource leak in 2.2.19?
@ 2001-11-05 22:09 Christian Lavoie
0 siblings, 0 replies; only message in thread
From: Christian Lavoie @ 2001-11-05 22:09 UTC (permalink / raw)
To: linux-kernel
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2001-11-05 22:09 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-11-05 22:09 File resource leak in 2.2.19? Christian Lavoie
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).