[lkml]   [2001]   [Nov]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectFile resource leak in 2.2.19?
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
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:12    [W:0.022 / U:1.172 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site