[Samba] Samba logs fill up disk with inotify errors, smbd 100% CPU
Please forgive me if direct email is not appropriate, but I am at my wit's end. I am running Kernel 2.6.35.2. Previously, I was running 2.6.32.something (don't know at this point). Samba is 3.4.8-59. I have been getting the inotify errors on both the old and the new Kernel, to the point that it filled my hard drive and made my Windows/XP unrecoverable. It appears to only happen when I am running Outlook on my Windows VM. Obviously, I normally run it all the time. Turning off notification is not a reasonable option. To get Windows to run, we restored to a version from June, but the inotify problem continued. So far, we have replaced the PST that my repetitive emails are sorted into, to eliminate the possibility that a corrupt PST is initiating a Windows Outlook problem/loop. Our next step would be to start a new OST, but that would put my email out of service for several hours as the OST is rebuilt. Nothing is wrong with the email messages involved. This inotify issue has been around for a long time, but there seems to be no resolution. Some of the comments in some of the forums suggest that the message is a debug message and shouldn't even be produced, and there were hints of a resolution for that. Is there one? I have lost most of the last three days because of this, and I really need some sort of resolution. After trying the OST rebuild, we would start all over with Linux, but that will cost me the better part of another day. Can you help? I can put you in touch with my techie (husband and/or son) if you want to work with them. They are both very knowledgeable. - Valerie Magee http://mageenet.net -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba logs fill up disk with inotify errors, smbd 100% CPU
On Tue, Aug 24, 2010 at 08:17:57AM -0400, Valerie L. Magee wrote: Please forgive me if direct email is not appropriate, but I am at my wit's end. As a workaround, try kernel change notify = no. This does not solve your problem though, but it should fix the immediate problem. Volker -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba logs fill up disk with inotify errors, smbd 100% CPU
Hello, One of the server I maintain has Ubuntu 8.04 LTS server with samba 3.0.28a. Kernel version is 2.6.24-16-server. The samba setup for this server is a workgroup environment, with user level security. At least once a week, sometimes more often, the server becomes unavailable because the system disk is full. It appears that the samba logs are the problem. Although the samba configuration file indicates that logs should be limited to 1000K, one of the machine specific logs (/var/log/samba/log.machine_xyz.old) grows to the point of entirely filling the disk (140 GB of log). The log file contains endless repetitions of the same message: smbd/notify_inotify.c:inotify_handler(240) No data on inotify fd?! At the same time, the smbd process for the user related to the faulty machine log uses 100% CPU, and must be stopped with kill -9. Note that it not always the same machine that creates the problem. Because some users are never affecting the system, we tried to identify if the origin of the problem was linked to a specific data manipulation by some of the 'bad' users, but we are still clueless. I found some info in this list with similarities to my problem where the suggestion is to include notify:inotify = false in [global] to see if it helps (http://www.mail-archive.com/samba%40lists.samba.org/msg98074.html) I've just done this, so I will have to wait and see. Otherwise, would you have any idea or suggestion ? Any help would be greatly appreciated. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba logs fill up disk with inotify errors, smbd 100% CPU
Am Dienstag, 17. März 2009 schrieb Stephane Carre: Hello, One of the server I maintain has Ubuntu 8.04 LTS server with samba 3.0.28a. Kernel version is 2.6.24-16-server. The samba setup for this server is a workgroup environment, with user level security. At least once a week, sometimes more often, the server becomes unavailable because the system disk is full. It appears that the samba logs are the problem. Although the samba configuration file indicates that logs should be limited to 1000K, one of the machine specific logs (/var/log/samba/log.machine_xyz.old) grows to the point of entirely filling the disk (140 GB of log). The log file contains endless repetitions of the same message: smbd/notify_inotify.c:inotify_handler(240) No data on inotify fd?! At the same time, the smbd process for the user related to the faulty machine log uses 100% CPU, and must be stopped with kill -9. Note that it not always the same machine that creates the problem. Because some users are never affecting the system, we tried to identify if the origin of the problem was linked to a specific data manipulation by some of the 'bad' users, but we are still clueless. I found some info in this list with similarities to my problem where the suggestion is to include notify:inotify = false in [global] to see if it helps (http://www.mail-archive.com/samba%40lists.samba.org/msg98074.html) I've just done this, so I will have to wait and see. Otherwise, would you have any idea or suggestion ? Any help would be greatly appreciated. looks like a buggy kernel. There have been kernel issues with inotify: http://ubuntuforums.org/showthread.php?t=655504 https://bugzilla.novell.com/show_bug.cgi?id=463372 Google will return more results... Cheers, Günter -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
