From: Andrew Masterson on
To fix the inotify problem use

kernel change notify = No

in your smb.conf. I am still experiencing this problem on RHEL 5.4
fully patched. As for the log files, the inotify errors did the same
thing to me (default size is 5M, and I got 100+GB log files)

-=Andrew

-----Original Message-----
From: samba-bounces(a)lists.samba.org
[mailto:samba-bounces(a)lists.samba.org] On Behalf Of Mike A. Leonetti
Sent: Thursday, April 29, 2010 7:53 AM
To: Samba Mailing
Subject: [Samba] 212GB log file generated for a workstation

Had a server fill up completely with a samba workstation log file. The
log file repeatedly had this information

[2010/04/29 04:00:01, 0] smbd/notify_inotify.c:inotify_handler(240)
No data on inotify fd?!

about a billion times.

In my smb.conf Ihave max log size = 50 set, so I was hoping the log file
wouldn't get that big.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
From: Jeremy Allison on
On Thu, Apr 29, 2010 at 12:02:46PM -0600, Andrew Masterson wrote:
> To fix the inotify problem use
>
> kernel change notify = No
>
> in your smb.conf. I am still experiencing this problem on RHEL 5.4
> fully patched. As for the log files, the inotify errors did the same
> thing to me (default size is 5M, and I got 100+GB log files)

This is a debug message that really shouldn't be at level 0.
But is unusual. Not sure if it's indicating a broken kernel
inotify system - but the inotify handler really shouldn't
get called if there are zero bytes to be read.

I'll fix up the debug message in the master tree.

Jeremy.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba