Page 1 of 2 12 LastLast
Results 1 to 10 of 40

Thread: "CIFS VFS" Error stalling/breaking shutdown - simple fix!

Hybrid View

  1. #1
    Join Date
    Oct 2008
    Location
    New Jersey
    Beans
    515
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Arrow "CIFS VFS" Error stalling/breaking shutdown - simple fix!

    There have been many threads on the forums/net about the CIFS shutdown bug, such as this and this.This bug can be easily found with several Google searches here and here.

    This bug occours in permanently mounted samba/cifs shares, due to a bug in the packages, in all versions of Ubuntu. The way the bug works is a problem with old code. The way the shutdown pattern works is it brings down the networking before it unmounts all permanent drives. You see, linux and the /etc/fstab were made in the 1970's, where the idea of a non-local drive was not yet established. Therefore, the code (runlevel 0) assumes that it's OK to take down networking before it attempts to unmount all filesystems. That's the way it's been forever, and it's unlikley to change.

    So, when cifs and samba roll along, and you permanently mount them in the fstab, you run into a snag, and that is this bug. Duh the cifs server is not responding to the disconnect command - networking is offline! (although some log output indicates otherwise!) This causes stalls and lock-ups on the shutdown, and can delay it by as much as 10 minutes! This is not good, obviously enough!

    The old way of fixing this was use a script (see the above thread) that would be generally a pain to implement (lotta chmoding, copying, a reboot, etc.) It could be done in an hour or so, but I didn't want to waste an hour, so i let it be.

    I was considering other options (such as a version of rc.local that would run at shutdown) while I looked through the Internet for ideas. I found one finally that suited my tastes for simplicity and workability. Heck, took two seconds to get working permanently. It's this command, that i found here:
    Code:
    sudo ln -s /etc/init.d/umountnfs.sh /etc/rc0.d/K15umountnfs.sh
    && sudo ln -s /etc/init.d/umountnfs.sh /etc/rc6.d/K15umountnfs.sh
    Too simple, but brilliant. It links the unmount nfs init command to the shutdown and reboot runlevels, and the runlevel runs these commands when it starts!
    ITS BLOODY GENIOUS CHAPS

    Enjoy, and have lots of fun not having to manually unmount your server every shutdown!
    Last edited by rhcm123; May 3rd, 2009 at 08:46 PM. Reason: cause it looks ugly
    OH NOES!!! I HAZ CRASHED SERVER!! WHY ON EARTH WOULD YOU DO THAT?!?! CAUSE ITS FUNNY!!!!
    Running either 7.04, 8.04, 8.10, 9.04, it varies.
    You talkin' to me? - Taxi Driver (1976)

  2. #2
    Join Date
    Mar 2006
    Location
    Kitakyushu Japan
    Beans
    9,361
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: "CIFS VFS" Error stalling/breaking shutdown - simple fix!

    This fix is also here: http://ubuntuforums.org/showthread.php?t=293513 but it's a bit outdated. The current version is available in that thread, but it's buried.

    I'm going to update my CIFS tutorial (2nd link in my sig), and link to this thread for the "CIFS VFS: Server not responding" fix.

    Thanks.

  3. #3
    Join Date
    Oct 2008
    Location
    New Jersey
    Beans
    515
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: "CIFS VFS" Error stalling/breaking shutdown - simple fix!

    Quote Originally Posted by dmizer View Post
    This fix is also here: http://ubuntuforums.org/showthread.php?t=293513 but it's a bit outdated. The current version is available in that thread, but it's buried.
    That's exactly why I made this thread. The first forum results on google are a bit outdated/buried in old threads, so i felt like making a new one so that when somebody googles their problem they don't get read only archive-results.
    OH NOES!!! I HAZ CRASHED SERVER!! WHY ON EARTH WOULD YOU DO THAT?!?! CAUSE ITS FUNNY!!!!
    Running either 7.04, 8.04, 8.10, 9.04, it varies.
    You talkin' to me? - Taxi Driver (1976)

  4. #4
    Join Date
    Nov 2007
    Beans
    41

    Re: "CIFS VFS" Error stalling/breaking shutdown - simple fix!

    Quote Originally Posted by rhcm123 View Post
    That's exactly why I made this thread. The first forum results on google are a bit outdated/buried in old threads, so i felt like making a new one so that when somebody googles their problem they don't get read only archive-results.
    Well, even after this fix, I still get the error. Any other idea or at least how can I debug it? This is really annoying.
    Visit my blog

  5. #5
    Join Date
    Nov 2007
    Beans
    41

    Re: "CIFS VFS" Error stalling/breaking shutdown - simple fix!

    Quote Originally Posted by gcastell View Post
    Well, even after this fix, I still get the error. Any other idea or at least how can I debug it? This is really annoying.
    Well, I should know better, the reason why I still get this error is because I am using Jaunty. dmizer post the solution in his tutorial
    Visit my blog

  6. #6
    Join Date
    May 2007
    Beans
    880
    Distro
    Ubuntu Development Release

    Question Re: "CIFS VFS" Error stalling/breaking shutdown - simple fix!

    I still get this error on my laptop running 64-bit Jaunty. I've tried the fix linked above (both in addition to the pre-Jaunty fix and also without those symbolic links, since the post isn't clear whether you need to do both). I've also tried using "S14" links in both places instead of "K15" (which is what works for me on my Jaunty desktop; the only difference that I can think of between my desktop and laptop is that the laptop is connected via wifi).

    Does anyone else have trouble with this still, and better yet has anyone figured out another solution?

  7. #7
    Join Date
    Aug 2007
    Beans
    371
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Question Re: "CIFS VFS" Error stalling/breaking shutdown - simple fix!

    Quote Originally Posted by rhcm123 View Post
    There have been many threads on the forums/net about the CIFS shutdown bug, such as this and this.This bug can be easily found with several Google searches here and here.

    This bug occours in permanently mounted samba/cifs shares, due to a bug in the packages, in all versions of Ubuntu. The way the bug works is a problem with old code. The way the shutdown pattern works is it brings down the networking before it unmounts all permanent drives. You see, linux and the /etc/fstab were made in the 1970's, where the idea of a non-local drive was not yet established. Therefore, the code (runlevel 0) assumes that it's OK to take down networking before it attempts to unmount all filesystems. That's the way it's been forever, and it's unlikley to change.

    So, when cifs and samba roll along, and you permanently mount them in the fstab, you run into a snag, and that is this bug. Duh the cifs server is not responding to the disconnect command - networking is offline! (although some log output indicates otherwise!) This causes stalls and lock-ups on the shutdown, and can delay it by as much as 10 minutes! This is not good, obviously enough!

    The old way of fixing this was use a script (see the above thread) that would be generally a pain to implement (lotta chmoding, copying, a reboot, etc.) It could be done in an hour or so, but I didn't want to waste an hour, so i let it be.

    I was considering other options (such as a version of rc.local that would run at shutdown) while I looked through the Internet for ideas. I found one finally that suited my tastes for simplicity and workability. Heck, took two seconds to get working permanently. It's this command, that i found here:
    Code:
    sudo ln -s /etc/init.d/umountnfs.sh /etc/rc0.d/K15umountnfs.sh
    && sudo ln -s /etc/init.d/umountnfs.sh /etc/rc6.d/K15umountnfs.sh
    Too simple, but brilliant. It links the unmount nfs init command to the shutdown and reboot runlevels, and the runlevel runs these commands when it starts!
    ITS BLOODY GENIOUS CHAPS

    Enjoy, and have lots of fun not having to manually unmount your server every shutdown!
    I am really new at this so forgive me.

    I did find out that the shutdown process drops the network and then tried to unmount the mounted network shares which causes it to hang for a couple of minutes.

    I manage (stumbling a little) to write a script that umounts (in reverse order of the fstab mount lines) then went to terminal to excute it.

    Code:
    sudo /home/username/scripts/dismount.sh
    This worked fine. Now shutting down was fast and no errors.

    Please (detailed step by step) what files and how do I need to put this working script in so it will go automatically.

    Thanks in advance

  8. #8
    Join Date
    Mar 2006
    Location
    Kitakyushu Japan
    Beans
    9,361
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: "CIFS VFS" Error stalling/breaking shutdown - simple fix!

    Quote Originally Posted by measekite View Post
    Please (detailed step by step) what files and how do I need to put this working script in so it will go automatically.
    See post 7: http://ubuntuforums.org/showpost.php...97&postcount=7

  9. #9
    Join Date
    Oct 2008
    Location
    New Jersey
    Beans
    515
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: "CIFS VFS" Error stalling/breaking shutdown - simple fix!

    Also, i noticed that if you switch interfaces that the server is interfacing on, this fix fails, unless you have used the share,

    For instance, if i mount the share over ethernet on my lappy (eth1) then unplug and go downstairs (eth0), this fix fails. However, if i go downstairs, then open a file on the server, this fix works. Hope this helps some of you.
    OH NOES!!! I HAZ CRASHED SERVER!! WHY ON EARTH WOULD YOU DO THAT?!?! CAUSE ITS FUNNY!!!!
    Running either 7.04, 8.04, 8.10, 9.04, it varies.
    You talkin' to me? - Taxi Driver (1976)

  10. #10
    Join Date
    Jul 2009
    Beans
    571
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: "CIFS VFS" Error stalling/breaking shutdown - simple fix!

    Help, there's no K15umountnfs.sh in my /etc/rc0 and /etc/rc6
    It's OK, everything we know will become obsolete at some time.

Page 1 of 2 12 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

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