mounted samba shares unavailable after suspend

Could you explain what you mean by "open a network share" ? Is it opening a smb:// location in Nautilus ? Or accessing a something that is mounted through /etc/fstab ?

Please include the information requested at https://wiki.ubuntu.com/DebuggingSamba#samba-client.

By "open a network share" I mean navigating to a folder that is shared on my local network, via a Samba server on another Ubuntu machine. To navigate to this folder I go to Places (from the main Ubuntu toolbar) > Network > Windows Network etc. I don't navigate to the folder directly via smb:// as I haven't learn that address and I haven't stored a shortcut to the folder.

Here is the info requested from the wiki page:

I believe the issue is with Samba as a client.
I can't say if this use to work with a previous release as I have only used 9.04 on this laptop and this is the first time I have used suspend.
Samba version in use is:

libsmbclient 2:3.3.2-1ubuntu3 samba install ok installed
libwbclient0 2:3.3.2-1ubuntu3 samba install ok installed
samba-common 2:3.3.2-1ubuntu3 samba install ok installed
smbclient 2:3.3.2-1ubuntu3 samba install ok installed
winbind 2:3.3.2-1ubuntu3 samba install ok installed

The remote share is accessed via Nautilus, invoked by going to the Place>Network menu option.
The remote server is running Ubuntu 8.04 LTS:
Domain=[MSHOME] OS=[Unix] Server=[Samba 3.0.28a]
Server requested LANMAN password (share-level security) but 'client lanman auth' is disabled
tree connect failed: SUCCESS - 0

Hope this helps, the lanman auth error shown above I have no clue about....
I also note that it seems that the error occurs more frequently if a network folder (so smb://server/documents) is auto-mounted on the desktop. After a suspend, I can't navigate to that folder by clicking on the icon on the desktop or via Places>Network>Windows Network>MSHome>Server>documents etc etc. If I then un-mount that folder, I can then navigate to that folder via Places>Network>Windows Network>MSHome>Server>documents.

Don't know if it helps, but here is a screencapture of the problem I am trying to explain above:

If possible can you include your samba log files when this happens and we can try to see what is going on?

Regards
chuck

No problems, but looking at samba.conf and then where the log files are meant to be, it seems there aren't any useful logs there.

Here is what I found.

Above was the samba.conf so you can check that (it is the stock afaik). I am now attaching the log files, though as I said, they seem empty.

more logs, but they seem non-informative.

and more.

Any update on this? I know it is hard to track down with no logs, but I betcha this can be replicated on any Ubuntu computer that goes into standby and is then powered on again.

So what happens if you restart samba after you suspend?

Regards
chuck

Restarting Samba doesn't make a difference, still the same error.

This doesn't occur if I Hibernate, instead of Suspend, it only occurs if I Suspend. Interestingly, if I Hibernate, clicking on the auto-created folder icon on the Desktop from one of the Network folders still gives an "The Folder is Of an Unknown Type" error. But navigating to the same folder via Network>Windows Network>MSHome>Server>Documents works no problem....

I have the exact same problem. Don't know if it helps, but I've noticed that disabling and re-enabling your wireless connection solves this issue. Also, I'm not sure if this is a samba-only problem. I can't reach the web interface from my bittorrent client either after suspend or hibernate. I'm not really an expert so I can't post any logs or more detailed information without your help. Using Karmic and Win7.

Best regards,

5oak

This might be more of a kernel issue.

Regards
chuck

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.

rupert, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder, but the one at the top) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

I still have this happen to me on ubuntu 14.04 LTS.

rpgmaker, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

Expired? This bug was there in Ubuntu 9 and is still there in 14.04. Argh.

dronus (paul-geisler), it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal: ubuntu-bug linux

Please feel free to subscribe me to it.

I reported a new one here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509664

Same issue here with Ubuntu 14.04.4 and kernel 4.2