linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ed Swierk <eswierk@cs.stanford.edu>
To: linux-kernel@vger.kernel.org
Subject: VFS: file-max limit reached when running on a virtual machine
Date: Thu, 19 Jan 2006 04:19:24 +0000 (UTC)	[thread overview]
Message-ID: <loom.20060119T045624-92@post.gmane.org> (raw)

I'm getting the error "VFS: file-max limit 50905 reached" on kernels 2.6.14 and
2.6.15, running on a qemu virtual machine configured with 512 MB of memory.  The
error occurs when I build a relatively large C++ program (the Boost library) on
the VM (which is otherwise idle).  It does not occur on kernels 2.6.11 or 2.6.13.

I understand that changes have been made recently to the way the kernel manages
file descriptors in order to improve real-time performance.

A thread back in October discussing these changes (subject: "VFS: file-max limit
50044 reached") seems to indicate that bad things can happen if certain
callbacks don't get called at regular intervals.  This situation seems quite
likely in a virtual machine environment where the frequency of timer interrupts
might vary by orders of magnitude depending on the workload of the host machine.

I have attempted a few workarounds, to no avail:

* increasing file-max (echo 100000 >/proc/sys/fs/file-max)
* setting clock=pit kernel parameter
* setting rcupdate.maxbatch=1000000 kernel parameter

Is there some other way to make the kernel less sensitive to ill-behaved
hardware timers, as it was pre-2.6.14, assuming that I am willing to sacrifice
real-time performance?

Any help would be appreciated.



             reply	other threads:[~2006-01-19  5:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-19  4:19 Ed Swierk [this message]
2006-01-21  8:24 ` VFS: file-max limit reached when running on a virtual machine Dipankar Sarma

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=loom.20060119T045624-92@post.gmane.org \
    --to=eswierk@cs.stanford.edu \
    --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;
as well as URLs for NNTP newsgroup(s).