Description of problem: The last small part of the file on a samba network can not be read (either copied by nautilus or cp or just read from gvfs mounted folder. Nautilus shows 'invalid argument' error message). Version-Release number of selected component (if applicable): 3.4.0-0.39.fc11.x86_64 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I'm seeing this as well... What would be the best way to gather some more information to track the problem down? I don't access Windows shares very often, but it's often enough to know that this problem only cropped up recently. When I get into work tomorrow I'll try some F11 and F12Alpha live CDs to see if this problem shows up there.
Created attachment 357934 [details] gvfsd-smb debug log Raising severity and priority, added K- for FEDORA-2009-7909 in bodhi (please don't push broken updates into stable repo). Reproducible with samba-3.4.0-0.39.fc11 and samba-3.4.0-0.41.fc12.1, seems like whole 3.4 series is affected. This is a major problem since users are unable to open (copy) any file from SMB share in Gnome. Small test showed issues in KDE as well. Both use libsmbclient. Standalone smbclient works fine though. Writing files showed no errors (haven't tested for content corruption). Tested against WinXP SP2, other users reported issues with Win2003 Server. No special characters in path or filename. Attached you can find debug log from gvfsd-smb (backend) serving client gvfs-copy command. There's nothing special in the code, just getting read function for context via smbc_getFunctionRead() and calling it afterwards for blocks smaller than 65536. Upstream Gnome bug is http://bugzilla.gnome.org/show_bug.cgi?id=588391
Rolling back to samba and libsmbclient 3.3.2-0.33.fc11.x86_64 solves the problem.
Ok, this is a bug in samba 3.4 libsmbclient (which just got fixed in master git tree), upstream bug is: https://bugzilla.samba.org/show_bug.cgi?id=6649. Anyway, the gvfs smb backend MUST set the buffer size to 65534 (which will drastically increase read performance). the code in http://git.gnome.org/cgit/gvfs/tree/daemon/gvfsbackendsmb.c#n715 MUST be changed into: if (bytes_requested > 65534) bytes_requested = 65534; In fact, not truncating the buffer size at all would gain even more performance (when talking to non-windows cifs servers).
I added the patch referenced in the samba bug report to what's in samba's F-11 cvs branch. I can now copy files off of windows shares.
(In reply to comment #4) > Anyway, the gvfs smb backend MUST set the buffer size to 65534 (which will > drastically increase read performance). Changes done in upstream, will get to rawhide next monday/tuesday. Günther, please backport the patch to rawhide packages at least, F11 is not so important as no samba-3.4.0 packages have been pushed to stable. Thanks!
Works properly in Fedora 12 and later versions in F11.
I'm seeing the same symptoms as this in F13 trying to copy files to a Windows server. When I drag a file to a share I get the following error: |----------------------------------------------------| | Error while copying "myplace-15h5uv2.jpg". | | | | There was an error copying the file into smb:// | | rwps-fs1/studentshared/shared. | | | | Show more details | | | | Invalid Argument | |----------------------------------------------------| I'm using samba-3.5.4-62.fc13.x86_64 and libsmbclient-3.5.4-62.fc13.x86_64
If I look at the properties of the files that I was copying to the server, then I see that 49152 bytes have been copied (out of a total of 233408 bytes).
Yep, same here. However, cp command seems to work fine. Problem occurs to me with nautilus.
Reopening by marking as 'Assigned' since bugzilla interface doesn't give me 'New' or 'Reopened' option.
Looks like a gnome-vfs2 bug
Please refer to upstream bugs: Gnome https://bugzilla.gnome.org/show_bug.cgi?id=633937 Samba https://bugzilla.samba.org/show_bug.cgi?id=7791
A Samba update has been issued that contains the fix mentioned in the upstream bugreport. Closing as fixed with current release.
The bug is back in F17. When I try write to a Windows 7 password protected share: $ gvfs-copy -p "img.png" "smb://sempron/documents/Blog" Error copying file img.png: Argumento inválido On the other way (copy from the Windows share) it works. gvfs-smb-1.11.5-1.fc17 libsmbclient-3.6.3-81.fc17.1
Please disconsider the above report. I don't know why but after a reinstall all works again.
(In reply to comment #16) > Please disconsider the above report. I don't know why but after a reinstall all > works again. Okay, feel free to open a new bugreport when you face this issue again. Most likely this is a samba problem as gvfsd-smb hasn't changed much past years and it heavily depends on libsmbclient.