On a little used desktop the script from comment 25 failed after 117
iterations, on the principal desktop, which has seemed slow recently, the
script failed on the first iteration attempt! Both machines running kernel
3.5.0-22
uname -a
Linux ionman 3.5.0-22-generic #34-Ubuntu SMP Tue Jan 8
Ok I posted a new fix here with the proper patch set:
http://people.canonical.com/~arges/lp1101666.1/
You should follow the new bug 1110605, where I have the test cases posted.
Let me know if there are any issues when testing on P/Q.
--
You received this bug notification because you are a
I see this bug too on real hardware: Linux epib-genstat3 3.2.0-36-generic
#57-Ubuntu SMP Tue Jan 8 21:44:52 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
This is on a server and showed up after 9 days of uptime. Furthermore, it
doesn't only show up when running tail -f, but also keeps libvirt-bin in a
Well, for now running
sysctl fs.inotify.max_user_instances=256
to increase the maximum number of instances (was 128) helps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101666
Title:
inotify fd
The patches that cause this issue were reverted.
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: linux (Ubuntu Precise)
Status: In Progress = Fix Committed
** Changed in: linux (Ubuntu Precise)
Status: Fix Committed = Fix Released
** Changed
I am using linux-image-3.2.0-37-generic (Version: 3.2.0-37.58) now and
did not experience the problem anymore (so far). At the very least the
new version does not appear to be harmful on my machine (i.e. I did not
notice any new bugs).
--
You received this bug notification because you are a
3.5.0-23-generic #35-Ubuntu fixes the problem for me on quantal.
** Tags removed: verification-needed-quantal
** Tags added: verification-done-quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The backported kernel 3.5.0-23.35~precise1 works fine, too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101666
Title:
inotify fd leak
To manage notifications about this bug go to:
I may be suffering from this. I'm on Ubuntu 12.04, uname says
3.2.0-36-generic-pae #57-Ubuntu,
# tail -f /var/log/syslog
complains
tail: inotify cannot be used, reverting to polling: Too many open files
and (oddly) dbus-daemon is using 79% of CPU according to top, and 17% according
to ps.
This
The attachment inotify/fanotify ref count fix of this bug report has
been identified as being a patch. The ubuntu-reviewers team has been
subscribed to the bug report so that they can review the patch. In the
event that this is in fact not a patch you can resolve this situation by
removing the
Lino, thanks a lot you for your time. Unfortunately, the patchset that
introduced this regression has been reverted from the Ubuntu kernels for
the time being. We will be bringing them back soon. We are currently
testing your patch, and reviewing our backport.
--
You received this bug
This bug is awaiting verification that the kernel for Precise in
-proposed solves the problem (3.2.0-37.58). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-precise' to 'verification-done-precise'.
If verification is not
This bug is awaiting verification that the kernel for Quantal in
-proposed solves the problem (3.5.0-23.35). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-quantal' to 'verification-done-quantal'.
If verification is not
** Tags removed: verification-needed-precise
** Tags added: verification-done-precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101666
Title:
inotify fd leak
To manage notifications about
3.2.0-37.58 (precise) works for me, i will test the backported quantal-
kernel as soon it becomes available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101666
Title:
inotify fd leak
To manage
** Branch linked: lp:ubuntu/precise-proposed/linux-lts-quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101666
Title:
inotify fd leak
To manage notifications about this bug go to:
First, thanks to Eugene and Adar for reporting and investigation.
I have had some time now to debug this and I found the reason for the bug.
Obviously something went wrong during
the port of the patch series mentioned above from mainline to ubuntu kernel:
There is the function fsnotify_destroy()
** Patch added: inotify/fanotify ref count fix
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1101666/+attachment/3499556/+files/fsnotify-inotify-call-destroy_group-in-inotify-fanot.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
@jsalisbury: As stated in #1101797 comment 4: Yes, 3.2.0-36 is also
affected, it introduced the bug into the 3.2 kernel line. The previuous
kernel, 3.2.0-35 is (still) working fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@markusj, There are actually two versions of 3.2.0-36. It appears
3.2.0-36.57 has the bug, since that is what the bug was reported
against. However, there is also 3.2.0-36.56. I was curious to see if
that version has the bug since it contains a different version of the
fsnotify patches.
--
** Changed in: linux (Ubuntu Precise)
Assignee: Joseph Salisbury (jsalisbury) = (unassigned)
** Changed in: linux (Ubuntu Quantal)
Assignee: Joseph Salisbury (jsalisbury) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I confirm Eugene's words:
darkk@darkk-ya-thinkpad:~$ cat /proc/sys/fs/inotify/max_user_instances
128
darkk@darkk-ya-thinkpad:~$ ls -l /proc/*/fd/ 2/dev/null | grep -c
anon_inode:inotify
36
darkk@darkk-ya-thinkpad:~$ sudo ls -l /proc/*/fd/ 2/dev/null | grep -c
anon_inode:inotify
51
Does this only happen when running Precise in a VM? Do you happen to
know if the bug also exists on bare metal?
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Tags added: regression-update
** Tags added: kernel-da-key
** Tags added: needs-bisect quantal
--
You received
@Adar, Do you happen to know that last Good and first Bad kernel
versions? If we can identify these two versions, I can perform a kernel
bisect to identify the commit that introduced this bug.
It appears you are running 3.2.0-36.57-generic. If this is correct, can
you test the following two
Happens on real amd64 iron here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101666
Title:
inotify fd leak
To manage notifications about this bug go to:
@Joseph, I see the bug on real hw, but I use quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101666
Title:
inotify fd leak
To manage notifications about this bug go to:
Running quantal.
The problem does NOT happen on this:
Linux pccross 3.5.0-21-generic #32-Ubuntu SMP Tue Dec 11 18:51:59 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux
The problem does happen on this:
Linux pccross 3.5.0-22-generic #34-Ubuntu SMP Tue Jan 8 21:47:00 UTC 2013
x86_64 x86_64 x86_64
I'm going to build a test kernel with the fsnotify patches reverted.
I'll post the kernel shortly.
This may also be related to bug 1101355 and bug 1101797
** Changed in: linux (Ubuntu Precise)
Status: Incomplete = In Progress
** Changed in: linux (Ubuntu Precise)
Status: In
** Changed in: linux (Ubuntu Precise)
Assignee: Joseph Salisbury (jsalisbury) = (unassigned)
** Changed in: linux (Ubuntu Quantal)
Assignee: Joseph Salisbury (jsalisbury) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Actually the quickest test would be to boot the 3.2.0-36.56 kernel and
see if it also exhibits this bug. It can be downloaded from:
https://launchpad.net/ubuntu/+source/linux/3.2.0-36.56
From that link, select your particular arch under the Builds section.
Thanks in advance!
** Changed in:
One additional request in addition to testing 3.2.0-36.56. Can folks
affected by this bug also test the v3.2.0-35 kernel, which can
downloaded from:
https://launchpad.net/ubuntu/+source/linux/3.2.0-35.55
Again, from that link, select your particular arch under the Builds
section.
Thanks in
I can confirm that Eugene's script yields the same results in my VM as
well:
...
62: ./eugene_script.sh: line 11: 10940 Terminated tail -f
/etc/hosts /dev/null
63: ./eugene_script.sh: line 11: 10943 Terminated tail -f
/etc/hosts /dev/null
64: tail: inotify cannot be
I would like to find out what goes wrong with inotifys user instance
counting but unfortunately I dont know how to reproduce this. @adar
could you be a little bit more precise in what your python unit tests
look like? Thx
--
You received this bug notification because you are a member of Ubuntu
#!/bin/bash
i=0
while [ $i -lt 1000 ];do
i=$((i+1))
echo -n $i:
tail -f /etc/hosts /dev/null
pid=$!
sleep 1
kill $pid
done
Running it gives this result:
[...]
65: /tmp/t.sh: line 11: 17838 Terminated tail -f /etc/hosts
/dev/null
66: /tmp/t.sh: line 11: 17840 Terminated
Thanks, Eugene. I had begun putting together a repro case with
pyinotify, but a shell + tail certainly takes the cake.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101666
Title:
inotify fd leak
I see this problem in quantal after kernel upgrade to 3.5.0-22-generic
#34-Ubuntu. Perhaps it's due to one of these:
10 days ago
Lino Sanfilippofsnotify: pass group to fsnotify_destroy_mark()
tree | commitdiff
10 days ago
Lino Sanfilippofsnotify: use reference counting for groups
tree |
And by the way, two unexpected manifestations are:
1. Sound applet disappear from the panel, and Sound settings do not show any
devices.
2. Dropbox applet turns red and reports Cannot access Dropbox folder
so there may be a lot of duplicate reports in distant areas of
launchpad...
--
You
** Attachment added: version.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1101666/+attachment/3488366/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101666
Title:
I should add that when I reboot the system, the problem goes away until
I run my pyinotify unit tests again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101666
Title:
inotify fd leak
To manage
apport information
** Tags added: apport-collected precise running-unity
** Description changed:
I'm running Ubuntu 12.04 in a VM. After a recent kernel upgrade, I'm
finding that I can reliably put the system in a position where the
inotify_init() syscall returns -EMFILE, but /proc/*/fd
40 matches
Mail list logo
