+ Post New Thread
Results 1 to 3 of 3
*nix Thread, smbd Failed to init inotify - Too many Files open in Technical; Now that we have moved all our data on a samba based storage we keep getting this error in syslog ...
  1. #1
    mdench's Avatar
    Join Date
    Oct 2011
    Location
    Billingshurst
    Posts
    770
    Thank Post
    36
    Thanked 102 Times in 92 Posts
    Rep Power
    38

    smbd Failed to init inotify - Too many Files open

    Now that we have moved all our data on a samba based storage we keep getting this error in syslog

    Code:
    Apr 16 07:56:29 trinity smbd[4888]: [2013/04/16 07:56:29.132674,  0] smbd/notify_inotify.c:297(inotify_setup)
    Apr 16 07:56:29 trinity smbd[4888]:   Failed to init inotify - Too many open files
    Apr 16 07:56:30 trinity smbd[4888]: [2013/04/16 07:56:30.250249,  0] smbd/notify_inotify.c:297(inotify_setup)
    Apr 16 07:56:30 trinity smbd[4888]:   Failed to init inotify - Too many open files
    Apr 16 07:56:30 trinity smbd[4888]: [2013/04/16 07:56:30.812052,  0] smbd/notify_inotify.c:297(inotify_setup)
    Apr 16 07:56:30 trinity smbd[4888]:   Failed to init inotify - Too many open files
    Apr 16 07:56:33 trinity smbd[4888]: [2013/04/16 07:56:33.652638,  0] smbd/notify_inotify.c:297(inotify_setup)
    Apr 16 07:56:33 trinity smbd[4888]:   Failed to init inotify - Too many open files
    Apr 16 07:56:38 trinity smbd[4888]: [2013/04/16 07:56:38.573648,  0] smbd/notify_inotify.c:297(inotify_setup)
    Apr 16 07:56:38 trinity smbd[4888]:   Failed to init inotify - Too many open files
    Apr 16 07:56:44 trinity smbd[4891]: [2013/04/16 07:56:44.348012,  0] smbd/notify_inotify.c:297(inotify_setup)
    Apr 16 07:56:44 trinity smbd[4891]:   Failed to init inotify - Too many open files
    Apr 16 07:56:44 trinity smbd[4891]: [2013/04/16 07:56:44.426425,  0] smbd/notify_inotify.c:297(inotify_setup)
    Apr 16 07:56:44 trinity smbd[4891]:   Failed to init inotify - Too many open files
    Apr 16 07:56:45 trinity smbd[4895]: [2013/04/16 07:56:45.682939,  0] smbd/notify_inotify.c:297(inotify_setup)
    Apr 16 07:56:45 trinity smbd[4895]:   Failed to init inotify - Too many open files
    Apr 16 07:56:47 trinity smbd[4895]: [2013/04/16 07:56:47.281783,  0] smbd/notify_inotify.c:297(inotify_setup)
    Apr 16 07:56:47 trinity smbd[4895]:   Failed to init inotify - Too many open files
    Apr 16 07:57:00 trinity smbd[4891]: [2013/04/16 07:57:00.727050,  0] smbd/notify_inotify.c:297(inotify_setup)
    Apr 16 07:57:00 trinity smbd[4891]:   Failed to init inotify - Too many open files
    Apr 16 07:57:02 trinity smbd[4895]: [2013/04/16 07:57:02.311698,  0] smbd/notify_inotify.c:297(inotify_setup)
    Apr 16 07:57:02 trinity smbd[4895]:   Failed to init inotify - Too many open files
    From what I've read on the interweb it's to do with the kernel notifying applications that a file has been changed somewhere on the file system and that we should change the values located in max_queued_events, max_user_instances, max_user_watches but so far haven't had any luck. Does any one else have any ideas that we could try?

  2. #2


    Join Date
    Jan 2006
    Posts
    8,202
    Thank Post
    442
    Thanked 1,032 Times in 812 Posts
    Rep Power
    339
    This is from the Redhat support portal:
    https://access.redhat.com/site/solutions/21601


    Resolution

    It looks like the well known max filedescriptors limit has reached. This can be changed with the fs.file-max sysctl tunable.

    Increasing the numbers in the following control files should resolve the issue.

    /proc/sys/fs/inotify/max_user_instances
    /proc/sys/fs/inotify/max_user_watches

    *man inotify*

    =====
    /proc/sys/fs/inotify/max_user_instances
    This specifies an upper limit on the number of inotify instances that can be created per real user ID.

    /proc/sys/fs/inotify/max_user_watches
    This specifies an upper limit on the number of watches that can be created per real user ID.
    =====
    Add the following line to /etc/sysctl.conf.

    fs.inotify.max_user_instances = <SPECIFY A NUMBER HERE>

    Run the command below.

    # sysctl -p
    In one of the case, increasing fs.file-max tunable with syctl does not resolved the issue.

    Root Cause

    One of the following limits has been reached:

    /proc/sys/fs/inotify/max_user_instances
    /proc/sys/fs/inotify/max_user_watches

  3. #3
    mdench's Avatar
    Join Date
    Oct 2011
    Location
    Billingshurst
    Posts
    770
    Thank Post
    36
    Thanked 102 Times in 92 Posts
    Rep Power
    38
    Cheers for that will Up the number in instances as we have watches set to 1048576 and see how we get on

SHARE:
+ Post New Thread

Similar Threads

  1. Replies: 16
    Last Post: 8th March 2013, 03:48 PM
  2. Too many connections to Server
    By Nick_Parker in forum Windows Server 2008
    Replies: 11
    Last Post: 2nd November 2012, 10:29 AM
  3. Too Many Files Open for Sharing
    By Davit2005 in forum Windows 7
    Replies: 3
    Last Post: 7th February 2012, 04:06 PM
  4. Vista/7 Fail to Install / Copy Files
    By EduTech in forum Windows
    Replies: 3
    Last Post: 12th February 2010, 05:55 AM
  5. Failed to copy files from CD
    By Dos_Box in forum Learning Network Manager
    Replies: 13
    Last Post: 12th April 2007, 10:42 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •