@the Polls! Your Vote is…..?
Loading ...Highest Rated
- Why is Linux Faster than Windows?
(5.00 out of 5) - Enable 5.1 Surround Sound on Linux – Ubuntu 8.04 Hardy (5.00 out of 5)
- 130 Useful Linux Based LiveCD Versions. (5.00 out of 5)
- The Simple Way to Get 5.1 Surround Sound Audio Working in Ub... (5.00 out of 5)
- Building a Web Developer / Designer PC Using Ubuntu Linux – ... (5.00 out of 5)
- Update Gimp in Ubuntu Hardy 8.04 – The Fast Way (5.00 out of 5)
- Top 12 Best Games for Ubuntu Linux – #4 World of Padman (5.00 out of 5)
- Windows User? Do You Wubi? (5.00 out of 5)
- Why is Linux Faster than Windows?
Dec
15
CIFS VFS Shutdown Error When Using SMBFS
December 15, 2009 | By: UbuntuLinuxHelp | 7 Comments
Posted in Linux Fixes
(1 votes, average: 4.00 out of 5)
Loading ...
I recently installed a fresh copy of Ubuntu Jaunty (9.04) and set up access to (DNS-321) my network shares using smbfs; as in the post "Sharing the Same Files Between Two PC’s". Shortly afterwards, when rebooting, shutting down, etc. I received this error message:
ACPID: Exiting
NM_SYSTEM_SETTING: SCPlugin-Ifupdown: Devices removed (UDI: /org/freedesktop/hal/devices/net_00_30_1B_BE_38_3D)
[601.136038] CIFS VFS: Server not responding
[601.136085] CIFS VFS: No response for CMD 50 mid 166
Then the system would sit for several seconds before doing anything. This never occurred with my Ubuntu 8.04 system (remembering that I installed and configured the network shares the same way).
Side note: For those not familiar, "VFS" refers to "Virtual File System" (node) and "CIFS" is "Common Internet File System). CIFS VFS is a virtual file system / project for Linux to allow access to servers and storage appliances. More from the documentation I found during research, is found on: http://linux-cifs.samba.org/
As near as I can surmise, since network-manager is installed, this is probably and issue where scripting for shutting down network-manager has higher priority than umount scripting and / or a permissions issue? A case in point is that the umount command would not work until I used sudo.
XKCD Comic - Make me a sandwich
Initially there were two ways I could fix this:
1) Various forums and site suggest removing network-manager from the system and configuring the network myself. It's a possibility, but I didn't want to do that.
2) Use terminal to sudo umount //192.168.3.10/sites && sudo umount //192.168.3.10/stock each time I wanted to restart, shutdown, etc. Again that's a possible solution, but annoying to keep having to do.
Strangely, Google was not helpful (for me) as there were only a few mentions of this error in returned search results, and I could not glean much from them.
I played with the idea of using a script to automatically run the root based umount command each time, but that became problematic for me (I'm not a developer), as I had trouble getting the script to work properly. I did find a thread on Ubuntu forums, "Cifs not unmounting and causing a problem even on shutdown" but it was removed (this link is to the Wayback Internet Archive, that still, luckily, had a copy of that content), and finally found another script already written by "max.durden" on the same forum: How to: Automatically umount cifs partitions.
I tried his solution and it worked! Because I'm worried about this thread also disappearing (I've encountered missing thread links several times on the forum), here are the steps below...
Download Max's fix file: mountcifs.zip
Extract the contents and copy the extracted file (named mountcifs) to the /etc/init.d/ directory (sudo cp mountcifs /etc/init.d/).
Make the file executable with the command sudo chmod +x mountcifs
Hard link that file using his names in the commands he specified in the original post:
cd /etc/rc0.d
sudo ln -s /etc/init.d/mountcifs K02mountcifs
cd /etc/rc6.d
sudo ln -s /etc/init.d/mountcifs K02mountcifs
The above fix works perfectly, no more errors, thanks to "Max" at Ubuntu Forums. It you have any questions about his fix, again, please visit his solution at http://ubuntuforums.org/showthread.php?t=293513 for much, much more information and follow up!
Related posts:
- Leave the Num Lock On!
- Do You Get the Firefox is Running Error?
- Sharing the Same Files Between Two PC’s
- Quick Fix: Black Desktop Background and Lost Icons
- 10 Things to do After Installing Ubuntu Linux
Comments
Weekly Top Commentors
jerry kovis (1)
UbuntuLinuxHelp (1)
UCR (1)
Victor (1)
[...] CIFS VFS Shutdown Error When Using SMBFS [...]
LOL, This is why Ubuntu is not more mainstream :)
I couldn’t even figure out the title of this post…
Nevertheless, I still like my Ubuntu machine
@doctorwinters
This is because I don’t only do things that the average mainstream user does. This was an issue I spawned when I re-created the network. I prefer to get into the network engineering aspects, play with hardware, software and get Linux to do interesting things.
Ubuntu is not more mainstream because people think Linux is hard, and believe it when they are told so. My father is almost 90 and he switched from Windows to Ubuntu with no problem adjusting, there are a group of kids down the street who use Ubuntu (mainly for gaming), they say it’s great. I’ve had business clients try it and they stuck with it. They all seem like mainstream people to me. :)
Again, it’s because of the assumptions of people, fortunately the notion that Linux is not for the “mainstream” is changing.
:) ;)
VFS errors occur because the network shuts down before network shares unmount. This issue has plagued Debian and Ubuntu for *years*. Various kludges may fix it for a while; but it’s now back with a vengence in Karmic.
Here’s the 20 page Ubuntu forums thread about attempted fixes and workarounds:
http://ubuntuforums.org/showth.....p?t=293513
The fundamental problem is a long-standing disagreement among Debian kernel and Network Manager developers about whose ‘fault’ it is, which paralyses all action. Users continue to suffer the consequences. Mainstream? Hardly!
@Agram
Appreciate the input, link and background info. :) – Thanks.
We are not saying Ubuntu is “Mainstream” (I even said “…not more mainstream because…”). We were suggesting why it’s not more mainstream. I indicated that more mainstream people are adopting it, that this is a growing trend.
If the disagreement between the kernel and network manager developers is a true scenario, then this is disgusting. Personally I find it shameful (and unprofessional) when two parties cannot come to some kind of compromise and get an issue fixed. It makes everyone else suffer and if the disagreement is true, it makes both parties look like egotistical idiots.
I should correct my hasty post. The disagreement was originally about Network Manager:
http://bugs.debian.org/cgi-bin.....bug=419049
But more recently the blame game involves the Debain developers and the Samba/CIFS developers.
Sander Merchal has been active on both the Debian and the Ubuntu forums about a fix for this issue, and is exasperated by the apathy that perpetuates it:
http://ubuntuforums.org/showpo.....stcount=81
You’ll see that his post refers to a bug report on Debian last year:
http://bugs.debian.org/cgi-bin.....bug=431966
As you can see from the ubuntuforums thread, the issue was first raised there in 2006. I don’t know how long before that it was first identified – may be someone who knows more than me can say. But three years is surely long enough for this to go on.
I entirely agree that Ubuntu, though not yet mainstream, is now more readily available to ordinary (i.e. not linux geeks) computer user. That’s surely why this kind of irritation is so damaging in terms of PR.
Anyway, all I really wanted to do was point out that the fix you suggest (Max Durden’s excellent script) appears no longer to work in Karmic, owing to changes introduced to the boot (and unmount) processes. :-(
[...] CIFS VFS Shutdown Error When Using SMBFS [...]