Announcement

Collapse
No announcement yet.

SMB share delays shutdown / a stop job is running

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    [SOLVED] SMB share delays shutdown / a stop job is running

    Hi,
    I added a smb share to my fstab. I tried various parameters in fstab, e.g.
    //192.168.0.7/public /home/marvin/odroid cifs guest 0 0
    or
    //192.168.0.7/public /home/marvin/odroid cifs guest,x-systemd.requires=network.target,x-systemd.automount,x-systemd.device-timeout=10,x-systemd.idle-timeout=1min 0 0
    The share mounts without issue, but during shutdown or reboot I get "a stop job is running" for 91sec.

    Anyone an idea, how to avoid the that behavior?

    I have seen this
    https://bugs.debian.org/cgi-bin/bugr...cgi?bug=798314
    which I tried
    and this
    https://www.kubuntuforums.net/showth...job+is+running

    #2
    One tip on researching is to limit results to a more recent time period. i usually limit it to one year unless I know a time frame. Those two results are a bit old, and not necessarily relevant

    However, having said that, can I guess that you are connecting via Wifi ?

    One thing to try is to go to your network connections section in System Settings and for your connection, go to the General Configuration tab and select "all users may connect to this network", which might be enough to fix this. The network connection could be closing when you log out as the user, but before the system un-mounts the share,, and if the connection is made 'global' the network connection stays open.


    https://github.com/systemd/systemd/issues/1435
    Lol, note this bug originated in 2015.
    The service files for wpa_supplicant in *buntu have these settings as mentioned in the report, but other users later on noted the network manager setting that seems to fix things.

    Comment


      #3
      I've outlined how I auto-mount in another forum and never get a "stop job running", well, not that I know of.
      https://www.wilderssecurity.com/thre...3#post-2925306

      Comment


        #4
        Originally posted by claydoh View Post
        One thing to try is to go to your network connections section in System Settings and for your connection, go to the General Configuration tab and select "all users may connect to this network", which might be enough to fix this. The network connection could be closing when you log out as the user, but before the system un-mounts the share,, and if the connection is made 'global' the network connection stays open.
        Perfect, that did the trick.
        Sometimes these necrotic posts are really helpful

        Comment


          #5
          Originally posted by Iangh View Post
          I've outlined how I auto-mount in another forum and never get a "stop job running", well, not that I know of.
          https://www.wilderssecurity.com/thre...3#post-2925306
          Thanks for helping. As the WiFi setting solved the issue, I did not try this one. Thanks anyway

          Comment


            #6
            Originally posted by marvin View Post
            ... these necrotic posts ...
            Usually in forums the word root "necro" is a reference to necromancy, bringing old threads back from the dead, but here I'm wondering what you mean. If you're disparaging your original question, no, not at all, IMO it's very valuable that questions like yours get asked.
            Regards, John Little

            Comment


              #7
              Originally posted by marvin View Post
              Perfect, that did the trick.
              Sometimes these necrotic posts are really helpful

              Well, despite setting a filter for a year in my search, the results did show the old bug report, which of course has a few very recent posts, so despite being annoyed by the old OP date, I have learned to not discount them completely

              Comment

              Working...
              X