I just started mounting my Windows shares on a kubuntu 14.04 system using the command .

All seemed fine until I had to reboot my Windows system and I had a window open in dolphin that was open to a folder on that mounted drive. I had opened Dolphin as root from the terminal (only way I know how) and all my terminal tabs in the window that opened dolphin froze as soon as I entered my home directory.

So, dolphin was open to /home/user/windows_share/music_folder and I could do nothing with that instance of dolphin or the split screen side that wasn't in the windows share, but it was on a folder within the home directory ~/Downloads.

In my terminal window that had 4 tabs open, I was able to use the tabs that weren't used to open Dolphin but as soon as I entered my home directory, it froze up.

I opened a new terminal, sudo su'd to get root, and then tried to kill -9 the PID of the root Dolphin instance. No go.

I checked the Windows machine to make sure the shares and password was correct and it was. I tried other file managers like Commander (root access) and same issue. I also couldn't kill it with kill -9 and the PID.

I finally decided to reboot so I saved relevant info and went to shutdown and then I realized that Dolphin had closed after about 10 mins of waiting.

My question is, how can this be avoided. I have NAS shares mounted via fstab basically the same way, except I use a .smbcredentials file for username and password. my NAS reboots once a day and I know my file manager has been open to these folders at times without any problems like this. Is this something only relevant to Windows? Is there something i can do to fix this a little easier if it happens again?

Much thanks to anyone who may be able to shed some light on this issue.

could this be caused by improper file naming on some particular file(s)? i.e. any "&" "/" or other characters that may be bad for wither linux or windows or both?