After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 617366 - 2 Gig limit copying file from samba share
2 Gig limit copying file from samba share
Status: RESOLVED NOTGNOME
Product: gvfs
Classification: Core
Component: smb backend
1.6.x
Other Linux
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2010-05-01 11:14 UTC by bartrouw
Modified: 2014-03-25 08:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Output of GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd -r (17.14 KB, text/plain)
2010-05-01 11:14 UTC, bartrouw
Details

Description bartrouw 2010-05-01 11:14:29 UTC
Created attachment 160094 [details]
Output of GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd -r

Probably this question is more related to samba functionality than to Nautilus.

Seems that nautilus doesn't support copying files larger than 2 Gig from a samba share.

The following error occurs when 2 Gig is copied:
Error while copying "xxx".
There was an error copying the file into xxx/xxx.
Show more details: Invalid argument.

I attached the output of 'GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd -r'. I deleted all the repeating GVfsJobRead debug info otherwise the dump would be over 2 MB with useless data. I left the beginning and the end unchanged.
I started logging just before I did the following:
Go to: Places -> Network -> [server] -> [sharedfolder]. Then I dragged the desired file to my Desktop.
The same error occurs when i use gvfs-copy.  

I had to manually mount the share with lfs option to succesfully copy a file with a size of aprox. 4 Gig.

kind regards.

Ubuntu 10.04 LTS - the Lucid Lynx, Desktop
Nautilus 2.30.0, package: 1:2.30.0-0ubuntu4
gvfs 1.6, package: 1.6.0+git20100414-0ubuntu1

I reported the same bug for Ubuntu 9 at https://bugs.launchpad.net/bugs/510938.
Comment 1 Ross Lagerwall 2014-03-25 08:05:51 UTC
Downstream bug report indicates that it was an smb server issue.