GNOME Bugzilla – Bug 729298
Cannot properly access SMB shares mounted by gvfs 1.20.1
Last modified: 2014-05-10 07:25:22 UTC
I recently upgraded from Ubuntu 13.10 to Ubuntu 14.04 and immediately encountered problems connecting to and accessing files in shares on my local network. Now that I am running Ubuntu 14.04 and version 1.20.1-1ubuntu1 of gvfs, every time I attempted to read a file (images, music, documents) from an SMB share on my network, the software I am using reports an IO error, an aborted connection, or a corrupted file. Previously I could either navigate to the share I wanted to access or use the "connect to server" option in Nautilus, and I could read and write to all files without any trouble. Now, however, when I make a connection I can sometimes get a directory listing, but any attempt to read files on those shares results in an error, usually along the lines of "software caused connection abort." This happens whether I am attempting to read a JPEG image, an MP3, or a Deja Dup backup. (For some reason, text files do not seem to cause any trouble.)
Several other people seem to be reporting this same problem: http://askubuntu.com/questions/450206/how-to-fix-a-software-caused-connection-abort-error-in-ubuntu-14-04 , https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1312362
I tested the latest upstream kernel and found the same problem. I tested a fresh copy of Ubuntu 14.04 running on a USB stick and found the same problem, so this bug is not limited to upgrades. I have tried creating a new user account and the problem persists. The problem seems to be related to the new version of gvfs, because mounting network shares without gvfs still works. (The only workaround I've been able to find so far has been to edit my /etc/fstab file to create a permanent mount point, but this isn't much of a solution.)
I would be happy to provide any logfiles or additional information in order to help diagnose and resolve this bug.
Thanks for the report.
Please run the following in a terminal:
pkill gvfs; GVFS_DEBUG=all GVFS_SMB_DEBUG=10 `find /usr/lib* -name 'gvfsd'` &> ~/log.txt
Then mount the smb share, reproduce the problem, and then upload log.txt in your home directory so we can see a log of what is happening. If possible, it would be good if you could do the same but reproduce the problem using the gvfs command-line tools; e.g. gvfs-copy smb://host/path/to/image.jpg ~/Downloads/image.jpg
Please also indicate what smb server you are using and whether you have any smb.conf changes.
Given the lack of changes between gvfs's smb backend in 13.10 and 14.04, I think it is quite likely that the issue is caused by samba, not gvfs. Thanks.
*** Bug 729010 has been marked as a duplicate of this bug. ***
As noted in the duplicated bug, this seems to be a libsmbclient issue, I have opened https://bugzilla.samba.org/show_bug.cgi?id=10584 in the meantime for it.
Created attachment 276202 [details]
Log from test case
Thanks so much for your reply and for opening the new bug case for the likely
libsmbclient issue. I carried out the tests you requested and am attaching the
log file they produced.
The server I'm contacting is running on a home NAS, an Iomega 2 TB Home Media
Network Hard Drive Cloud Edition. Beyond that I'm not sure what specific
software the server is running. I'll do some checking and will get back to you
on that point.
In the meantime, let me know if there's anything else I can do to help diagnose
Yeah, this problem seems to be a common issue on these Iomega NAS devices with Samba 4.
Here's the error coming from libsmbclient:
map_errno_from_nt_status: 32 bit codes: code=c00000b5
smbc errno NT_STATUS_IO_TIMEOUT -> 110
There's little we can do from gvfs; however, I'm sure the Samba developers would like you to capture a wire trace and upload it to the previously mentioned Samba bug.
Will do. Thanks again for pointing me in the right direction.
Maybe the info at this url can help to determine the server configuration:
I'm having the same trouble with the Medion MD86803. Which is also a 2TB portable NAS device.
Thanks, Jan. I can now confirm that my NAS is running Samba 3.0.32. I've gone ahead and updated the bug here: https://bugzilla.samba.org/show_bug.cgi?id=10584
Closing since we have an upstream bug now...