(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Sun, 22 Feb 2009 16:32:47 -0800 (PST) bugme-daemon@xxxxxxxxxxxxxxxxxxx wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=12754 > > Summary: inotify doesn't free memory allocated to watches > Product: File System > Version: 2.5 > KernelVersion: 2.6.28 > Platform: All > OS/Version: Linux > Tree: Mainline > Status: NEW > Severity: normal > Priority: P1 > Component: Other > AssignedTo: fs_other@xxxxxxxxxxxxxxxxxxxx > ReportedBy: russell@xxxxxxxxxxxxxxx > > > Latest working kernel version: none > Earliest failing kernel version: > Distribution: CentOS 5 > Hardware Environment: intel > Software Environment: > Problem Description: run out of watches > > Steps to reproduce: use enough watches > > We have webcams that take photos every 5 minutes. I run a daemon > that detects the creation of a new webcam photo then makes a thumbnail > of it. Eventually it stopped working. I figured out that I could > not create new watches: inotify_add_watch reported "No space left on device". > I create all the watches with the ONESHOT parameter so they are deleted > as soon as they are triggered. When I make it display the watch number > it's always 3. A new watch is added only when the old watch has been > triggered. inotify isn't recovering the memory from deleted watches. > So we have a serious leak. A few fixes have gone into inotify since 2.6.28. I don't immediately see any which would address this bug, but it would be worth testing 2.6.29-rc6 if poss, please. Hopefully those fixes also got fed back into 2.6.28.x, but that path is somewhat unreliable. If it isn't yet fixed then I'm not sure how to get it fixed, really - inotify development is a bit quiet. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
