← Back to team overview

kernel-packages team mailing list archive

[Bug 404917] Re: mounted samba shares unavailable after suspend


Then it was 3 years later....

My symptom is: After I suspend, my samba mount points are still active
in my mount list. But when I navigate to one of them, my terminal
crashes - fatally. I can't ctrl-c or ctrl-z out of it anymore. Also
crashes when I navigate to their parent folder and do: ls

If I do: sudo umount -f [share] then sometimes it works, but sometimes
it says it is still busy. The latter is the most annoying because then I
can't remount it in the same location.

But you are right, chuck, probably it is a kernal issue.

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  mounted samba shares unavailable after suspend

Status in “linux” package in Ubuntu:

Bug description:
  I have noticed this happen every time I open my laptop running 9.04
  that has been suspended.

  If before suspend, I open a network share (that is actually a Samba
  share on another Ubuntu machine (8.04) and then allow the machine to
  go into suspend (by closing the lid) and then open the lid again
  sometime later, after the machine is running again, I can no longer
  access the shared folder (either via the icon on the desktop or via

  I get an error saying: Could not display XXXXX. The file is of an
  unknown type.

  Then if I try to browse  any of my Samba network shares, I more often
  than not get no results. If I click on Places>Network, I get to see
  Windows Network, but if I click on that, I get an empty blank nautilus
  window. If I then click back, I can then go one further, so I can
  click through Places>Network>Windows Networks> MSHome, but then it is
  blank. Then if I click back all the way, then I try again, then I can
  go one further again, so Place>Network>Windows Network>MSHome>Server,
  but then it is blank. This continues until I can finally get to the
  folders and everything is ok.

  If I shutdown instead of hibernate and then restart, this problem
  never occurs....

  I am using a wireless connection, but I wait until I get the Connected
  notification before I do anything, so I definatley have network

  The logs dont seem to show anything relevant, but I may be wrong.

To manage notifications about this bug go to: