From: "David Turner" <novalis@novalis.org>
To: "John McCutchan" <john@johnmccutchan.com>,
"Robert Love" <rlove@rlove.org>,
"Eric Paris" <eparis@parisplace.org>,
linux-kernel@vger.kernel.org
Subject: PROBLEM: Inotify leaks file descriptors.
Date: Tue, 4 Mar 2014 14:09:18 -0500 [thread overview]
Message-ID: <daed65ee080e4cc417c87f34af8447f2.squirrel@webmail.novalis.org> (raw)
I apologize for the slightly convoluted reproduction steps here,
but I was not easily able to find a simpler test case in the
time that I had available.
First, you'll need Facebook's watchman:
https://github.com/facebook/watchman
Build and install it. Then run the attached Python script.
After a few hundred lines, you'll start to see errors of the form
inotify_init error: Too many open files. That could just
indicate that watchman is leaking, but I think that's not what's
going on, because killing watchman does not fix the problem.
To demonstrate, kill the python script, then kill watchman.
Then run tail -f /etc/hosts. You'll get "tail: inotify cannot be
used, reverting to polling: Too many open files" (you may need to
run a few tails to see the error). In fact, the only way I have
found to get back to normal is to reboot.
I tried increasing the ulimit to 10000 (from the default 1024).
The error still happens, but it seems to take a bit longer.
I have tried on a couple of Ubuntu kernels:
Linux version 3.11.0-17-generic (buildd@toyol) (gcc version 4.6.3
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #31~precise1-Ubuntu SMP Tue Feb 4
21:25:43 UTC 2014
And Ubuntu's 3.8.0-36-generic (it's not running right now so I can't give
the full version).
I've also tried a stock kernel built from source (in a virtualbox):
Linux version 3.13.5 (dturner@dturner-virtualbox) (gcc version 4.8.1
(Ubuntu/Linaro 4.8.1-10ubuntu8) ) #1 SMP Mon Mar 3 20:41:51 EST 2014
I get the error on all of these.
There is no output in dmesg.
I was running these tests on ext4 filesystems:
(for the Ubuntu kernels)
/dev/mapper/stross--vg-root on / type ext4 (rw,errors=remount-ro)
(for the stock kernel, in the virtualbox)
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
Please let me know if you need any more information.
FWIW, I did find this bug while googling, but it was on older kernels and
was allegedly fixed:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1101666
next reply other threads:[~2014-03-04 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 19:09 David Turner [this message]
2014-03-04 19:18 ` David Turner
2014-03-07 5:59 ` David Turner
2014-03-19 13:16 ` Jan Kara
2014-03-04 19:18 ` David Turner
2014-03-11 21:42 ` Jan Kara
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=daed65ee080e4cc417c87f34af8447f2.squirrel@webmail.novalis.org \
--to=novalis@novalis.org \
--cc=eparis@parisplace.org \
--cc=john@johnmccutchan.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlove@rlove.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®