Failed to add /run/systemd/ask-password to directory watch: No space left on device?











up vote
26
down vote

favorite
9












Does anyone knows why have I this message with the new update of samba on ubuntu 16.04.1?



Paramétrage de samba (2:4.3.9+dfsg-0ubuntu0.16.04.3) ...
Failed to add /run/systemd/ask-password to directory watch: No space left on device:


Since I have so much space, I don't understand :



df -h
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
udev 16G 0 16G 0% /dev
tmpfs 3,2G 11M 3,2G 1% /run
/dev/sda2 107G 49G 53G 48% /
tmpfs 16G 184K 16G 1% /dev/shm
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/sdi2 367G 343G 5,2G 99% /media/divers
/dev/sda1 110G 366M 104G 1% /opt
/dev/sdm1 147G 136G 11G 93% /media/nfsmedia/syno/usb4
/dev/sdq1 74G 69G 1,1G 99% /media/nfsmedia/syno/usb8
/dev/sdp1 459G 453G 5,6G 99% /media/nfsmedia/syno/usb1
/dev/sde2 735G 684G 14G 99% /media/series
/dev/sdo1 1,8T 1015G 726G 59% /media/nfsmedia/syno/usb3
/dev/sdr1 74G 68G 1,6G 98% /media/nfsmedia/syno/usb7
/dev/mapper/RAIDSTOCK-RAID5FSTOCK 9,0T 7,3T 1,4T 85% /media/RAIDFORSTOCK
/dev/mapper/RAID1FORDOCK-DOCK 550G 303G 220G 58% /media/DOCK
cgmfs 100K 0 100K 0% /run/cgmanager/fs
tmpfs 3,2G 0 3,2G 0% /run/user/1004
//192.168.6.12/vigilian 1,9T 1,7T 179G 91% /media/smbseries/nsa
//192.168.6.11/NASA 930G 807G 123G 87% /media/smbseries/nasa
tmpfs 3,2G 12K 3,2G 1% /run/user/123
tmpfs 3,2G 0 3,2G 0% /run/user/1000









share|improve this question


























    up vote
    26
    down vote

    favorite
    9












    Does anyone knows why have I this message with the new update of samba on ubuntu 16.04.1?



    Paramétrage de samba (2:4.3.9+dfsg-0ubuntu0.16.04.3) ...
    Failed to add /run/systemd/ask-password to directory watch: No space left on device:


    Since I have so much space, I don't understand :



    df -h
    Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
    udev 16G 0 16G 0% /dev
    tmpfs 3,2G 11M 3,2G 1% /run
    /dev/sda2 107G 49G 53G 48% /
    tmpfs 16G 184K 16G 1% /dev/shm
    tmpfs 5,0M 4,0K 5,0M 1% /run/lock
    tmpfs 16G 0 16G 0% /sys/fs/cgroup
    /dev/sdi2 367G 343G 5,2G 99% /media/divers
    /dev/sda1 110G 366M 104G 1% /opt
    /dev/sdm1 147G 136G 11G 93% /media/nfsmedia/syno/usb4
    /dev/sdq1 74G 69G 1,1G 99% /media/nfsmedia/syno/usb8
    /dev/sdp1 459G 453G 5,6G 99% /media/nfsmedia/syno/usb1
    /dev/sde2 735G 684G 14G 99% /media/series
    /dev/sdo1 1,8T 1015G 726G 59% /media/nfsmedia/syno/usb3
    /dev/sdr1 74G 68G 1,6G 98% /media/nfsmedia/syno/usb7
    /dev/mapper/RAIDSTOCK-RAID5FSTOCK 9,0T 7,3T 1,4T 85% /media/RAIDFORSTOCK
    /dev/mapper/RAID1FORDOCK-DOCK 550G 303G 220G 58% /media/DOCK
    cgmfs 100K 0 100K 0% /run/cgmanager/fs
    tmpfs 3,2G 0 3,2G 0% /run/user/1004
    //192.168.6.12/vigilian 1,9T 1,7T 179G 91% /media/smbseries/nsa
    //192.168.6.11/NASA 930G 807G 123G 87% /media/smbseries/nasa
    tmpfs 3,2G 12K 3,2G 1% /run/user/123
    tmpfs 3,2G 0 3,2G 0% /run/user/1000









    share|improve this question
























      up vote
      26
      down vote

      favorite
      9









      up vote
      26
      down vote

      favorite
      9






      9





      Does anyone knows why have I this message with the new update of samba on ubuntu 16.04.1?



      Paramétrage de samba (2:4.3.9+dfsg-0ubuntu0.16.04.3) ...
      Failed to add /run/systemd/ask-password to directory watch: No space left on device:


      Since I have so much space, I don't understand :



      df -h
      Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
      udev 16G 0 16G 0% /dev
      tmpfs 3,2G 11M 3,2G 1% /run
      /dev/sda2 107G 49G 53G 48% /
      tmpfs 16G 184K 16G 1% /dev/shm
      tmpfs 5,0M 4,0K 5,0M 1% /run/lock
      tmpfs 16G 0 16G 0% /sys/fs/cgroup
      /dev/sdi2 367G 343G 5,2G 99% /media/divers
      /dev/sda1 110G 366M 104G 1% /opt
      /dev/sdm1 147G 136G 11G 93% /media/nfsmedia/syno/usb4
      /dev/sdq1 74G 69G 1,1G 99% /media/nfsmedia/syno/usb8
      /dev/sdp1 459G 453G 5,6G 99% /media/nfsmedia/syno/usb1
      /dev/sde2 735G 684G 14G 99% /media/series
      /dev/sdo1 1,8T 1015G 726G 59% /media/nfsmedia/syno/usb3
      /dev/sdr1 74G 68G 1,6G 98% /media/nfsmedia/syno/usb7
      /dev/mapper/RAIDSTOCK-RAID5FSTOCK 9,0T 7,3T 1,4T 85% /media/RAIDFORSTOCK
      /dev/mapper/RAID1FORDOCK-DOCK 550G 303G 220G 58% /media/DOCK
      cgmfs 100K 0 100K 0% /run/cgmanager/fs
      tmpfs 3,2G 0 3,2G 0% /run/user/1004
      //192.168.6.12/vigilian 1,9T 1,7T 179G 91% /media/smbseries/nsa
      //192.168.6.11/NASA 930G 807G 123G 87% /media/smbseries/nasa
      tmpfs 3,2G 12K 3,2G 1% /run/user/123
      tmpfs 3,2G 0 3,2G 0% /run/user/1000









      share|improve this question













      Does anyone knows why have I this message with the new update of samba on ubuntu 16.04.1?



      Paramétrage de samba (2:4.3.9+dfsg-0ubuntu0.16.04.3) ...
      Failed to add /run/systemd/ask-password to directory watch: No space left on device:


      Since I have so much space, I don't understand :



      df -h
      Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
      udev 16G 0 16G 0% /dev
      tmpfs 3,2G 11M 3,2G 1% /run
      /dev/sda2 107G 49G 53G 48% /
      tmpfs 16G 184K 16G 1% /dev/shm
      tmpfs 5,0M 4,0K 5,0M 1% /run/lock
      tmpfs 16G 0 16G 0% /sys/fs/cgroup
      /dev/sdi2 367G 343G 5,2G 99% /media/divers
      /dev/sda1 110G 366M 104G 1% /opt
      /dev/sdm1 147G 136G 11G 93% /media/nfsmedia/syno/usb4
      /dev/sdq1 74G 69G 1,1G 99% /media/nfsmedia/syno/usb8
      /dev/sdp1 459G 453G 5,6G 99% /media/nfsmedia/syno/usb1
      /dev/sde2 735G 684G 14G 99% /media/series
      /dev/sdo1 1,8T 1015G 726G 59% /media/nfsmedia/syno/usb3
      /dev/sdr1 74G 68G 1,6G 98% /media/nfsmedia/syno/usb7
      /dev/mapper/RAIDSTOCK-RAID5FSTOCK 9,0T 7,3T 1,4T 85% /media/RAIDFORSTOCK
      /dev/mapper/RAID1FORDOCK-DOCK 550G 303G 220G 58% /media/DOCK
      cgmfs 100K 0 100K 0% /run/cgmanager/fs
      tmpfs 3,2G 0 3,2G 0% /run/user/1004
      //192.168.6.12/vigilian 1,9T 1,7T 179G 91% /media/smbseries/nsa
      //192.168.6.11/NASA 930G 807G 123G 87% /media/smbseries/nasa
      tmpfs 3,2G 12K 3,2G 1% /run/user/123
      tmpfs 3,2G 0 3,2G 0% /run/user/1000






      apt 16.04 updates samba






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Sep 23 '16 at 16:55









      vigilian

      1791312




      1791312






















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          3
          down vote



          accepted










          I'm not reputable enough to comment on the accepted answer, but I wanted to say that it's by no means limited to CrashPlan. Dropbox and other file sharing platforms use inotify watches per inode to detect when an upstream sync needs to occur. Malware detectors may have watches on directories. Other backup tools besides CrashPlan might, as well.



          To see what's consuming inotify watches, use lsof:



          sudo lsof -K | grep inotify | (less||more||pg)





          share|improve this answer




























            up vote
            54
            down vote













            As discussed in a Red Hat bug report, it turns out that the Crashplan back-up service is the most likely culprit. It uses many inotify watches and, eventually, eats them all up.



            The immediate fix is to run:



            sudo -i
            echo 1048576 > /proc/sys/fs/inotify/max_user_watches
            exit


            to make more watches available.



            The long-term fix is to edit the file /etc/sysctl.conf to include the line:



            fs.inotify.max_user_watches=1048576





            share|improve this answer























            • yes, I've seen it but it wasn't that since I don't have anything like it installed. It seems that iwas samba related or RAID related
              – vigilian
              Oct 30 '16 at 12:14






            • 7




              This helped me, I have Crashplan
              – Brian Low
              Nov 19 '16 at 22:29










            • but anyway it stills works. So be aware that it would be a similar problem with too much mdadm notification or smaba notification.
              – vigilian
              Jul 29 '17 at 23:16










            • Helped me on kali linux
              – Tim Jonas
              Nov 21 '17 at 11:12











            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "89"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














             

            draft saved


            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f828779%2ffailed-to-add-run-systemd-ask-password-to-directory-watch-no-space-left-on-dev%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            3
            down vote



            accepted










            I'm not reputable enough to comment on the accepted answer, but I wanted to say that it's by no means limited to CrashPlan. Dropbox and other file sharing platforms use inotify watches per inode to detect when an upstream sync needs to occur. Malware detectors may have watches on directories. Other backup tools besides CrashPlan might, as well.



            To see what's consuming inotify watches, use lsof:



            sudo lsof -K | grep inotify | (less||more||pg)





            share|improve this answer

























              up vote
              3
              down vote



              accepted










              I'm not reputable enough to comment on the accepted answer, but I wanted to say that it's by no means limited to CrashPlan. Dropbox and other file sharing platforms use inotify watches per inode to detect when an upstream sync needs to occur. Malware detectors may have watches on directories. Other backup tools besides CrashPlan might, as well.



              To see what's consuming inotify watches, use lsof:



              sudo lsof -K | grep inotify | (less||more||pg)





              share|improve this answer























                up vote
                3
                down vote



                accepted







                up vote
                3
                down vote



                accepted






                I'm not reputable enough to comment on the accepted answer, but I wanted to say that it's by no means limited to CrashPlan. Dropbox and other file sharing platforms use inotify watches per inode to detect when an upstream sync needs to occur. Malware detectors may have watches on directories. Other backup tools besides CrashPlan might, as well.



                To see what's consuming inotify watches, use lsof:



                sudo lsof -K | grep inotify | (less||more||pg)





                share|improve this answer












                I'm not reputable enough to comment on the accepted answer, but I wanted to say that it's by no means limited to CrashPlan. Dropbox and other file sharing platforms use inotify watches per inode to detect when an upstream sync needs to occur. Malware detectors may have watches on directories. Other backup tools besides CrashPlan might, as well.



                To see what's consuming inotify watches, use lsof:



                sudo lsof -K | grep inotify | (less||more||pg)






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Sep 21 at 19:01









                dgc

                461




                461
























                    up vote
                    54
                    down vote













                    As discussed in a Red Hat bug report, it turns out that the Crashplan back-up service is the most likely culprit. It uses many inotify watches and, eventually, eats them all up.



                    The immediate fix is to run:



                    sudo -i
                    echo 1048576 > /proc/sys/fs/inotify/max_user_watches
                    exit


                    to make more watches available.



                    The long-term fix is to edit the file /etc/sysctl.conf to include the line:



                    fs.inotify.max_user_watches=1048576





                    share|improve this answer























                    • yes, I've seen it but it wasn't that since I don't have anything like it installed. It seems that iwas samba related or RAID related
                      – vigilian
                      Oct 30 '16 at 12:14






                    • 7




                      This helped me, I have Crashplan
                      – Brian Low
                      Nov 19 '16 at 22:29










                    • but anyway it stills works. So be aware that it would be a similar problem with too much mdadm notification or smaba notification.
                      – vigilian
                      Jul 29 '17 at 23:16










                    • Helped me on kali linux
                      – Tim Jonas
                      Nov 21 '17 at 11:12















                    up vote
                    54
                    down vote













                    As discussed in a Red Hat bug report, it turns out that the Crashplan back-up service is the most likely culprit. It uses many inotify watches and, eventually, eats them all up.



                    The immediate fix is to run:



                    sudo -i
                    echo 1048576 > /proc/sys/fs/inotify/max_user_watches
                    exit


                    to make more watches available.



                    The long-term fix is to edit the file /etc/sysctl.conf to include the line:



                    fs.inotify.max_user_watches=1048576





                    share|improve this answer























                    • yes, I've seen it but it wasn't that since I don't have anything like it installed. It seems that iwas samba related or RAID related
                      – vigilian
                      Oct 30 '16 at 12:14






                    • 7




                      This helped me, I have Crashplan
                      – Brian Low
                      Nov 19 '16 at 22:29










                    • but anyway it stills works. So be aware that it would be a similar problem with too much mdadm notification or smaba notification.
                      – vigilian
                      Jul 29 '17 at 23:16










                    • Helped me on kali linux
                      – Tim Jonas
                      Nov 21 '17 at 11:12













                    up vote
                    54
                    down vote










                    up vote
                    54
                    down vote









                    As discussed in a Red Hat bug report, it turns out that the Crashplan back-up service is the most likely culprit. It uses many inotify watches and, eventually, eats them all up.



                    The immediate fix is to run:



                    sudo -i
                    echo 1048576 > /proc/sys/fs/inotify/max_user_watches
                    exit


                    to make more watches available.



                    The long-term fix is to edit the file /etc/sysctl.conf to include the line:



                    fs.inotify.max_user_watches=1048576





                    share|improve this answer














                    As discussed in a Red Hat bug report, it turns out that the Crashplan back-up service is the most likely culprit. It uses many inotify watches and, eventually, eats them all up.



                    The immediate fix is to run:



                    sudo -i
                    echo 1048576 > /proc/sys/fs/inotify/max_user_watches
                    exit


                    to make more watches available.



                    The long-term fix is to edit the file /etc/sysctl.conf to include the line:



                    fs.inotify.max_user_watches=1048576






                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Mar 29 '17 at 17:23









                    jordanbtucker

                    1033




                    1033










                    answered Oct 14 '16 at 23:27









                    LandonL

                    64152




                    64152












                    • yes, I've seen it but it wasn't that since I don't have anything like it installed. It seems that iwas samba related or RAID related
                      – vigilian
                      Oct 30 '16 at 12:14






                    • 7




                      This helped me, I have Crashplan
                      – Brian Low
                      Nov 19 '16 at 22:29










                    • but anyway it stills works. So be aware that it would be a similar problem with too much mdadm notification or smaba notification.
                      – vigilian
                      Jul 29 '17 at 23:16










                    • Helped me on kali linux
                      – Tim Jonas
                      Nov 21 '17 at 11:12


















                    • yes, I've seen it but it wasn't that since I don't have anything like it installed. It seems that iwas samba related or RAID related
                      – vigilian
                      Oct 30 '16 at 12:14






                    • 7




                      This helped me, I have Crashplan
                      – Brian Low
                      Nov 19 '16 at 22:29










                    • but anyway it stills works. So be aware that it would be a similar problem with too much mdadm notification or smaba notification.
                      – vigilian
                      Jul 29 '17 at 23:16










                    • Helped me on kali linux
                      – Tim Jonas
                      Nov 21 '17 at 11:12
















                    yes, I've seen it but it wasn't that since I don't have anything like it installed. It seems that iwas samba related or RAID related
                    – vigilian
                    Oct 30 '16 at 12:14




                    yes, I've seen it but it wasn't that since I don't have anything like it installed. It seems that iwas samba related or RAID related
                    – vigilian
                    Oct 30 '16 at 12:14




                    7




                    7




                    This helped me, I have Crashplan
                    – Brian Low
                    Nov 19 '16 at 22:29




                    This helped me, I have Crashplan
                    – Brian Low
                    Nov 19 '16 at 22:29












                    but anyway it stills works. So be aware that it would be a similar problem with too much mdadm notification or smaba notification.
                    – vigilian
                    Jul 29 '17 at 23:16




                    but anyway it stills works. So be aware that it would be a similar problem with too much mdadm notification or smaba notification.
                    – vigilian
                    Jul 29 '17 at 23:16












                    Helped me on kali linux
                    – Tim Jonas
                    Nov 21 '17 at 11:12




                    Helped me on kali linux
                    – Tim Jonas
                    Nov 21 '17 at 11:12


















                     

                    draft saved


                    draft discarded



















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f828779%2ffailed-to-add-run-systemd-ask-password-to-directory-watch-no-space-left-on-dev%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    How to change which sound is reproduced for terminal bell?

                    Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents

                    Can I use Tabulator js library in my java Spring + Thymeleaf project?