Bug 110703 - 4GB file limit when copying to SMB shares
Summary: 4GB file limit when copying to SMB shares
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-vfs2-extras   
(Show other bugs)
Version: 1
Hardware: i686 Linux
medium
medium
Target Milestone: ---
Assignee: Alexander Larsson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-11-23 18:41 UTC by István Tóth
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-03-03 16:02:29 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description István Tóth 2003-11-23 18:41:02 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031030

Description of problem:
The SMB VFS component corrupts 4GB+ files when copying to a WinXP share

Version-Release number of selected component (if applicable):
gnome-vfs2-extras-0.99.10-3.1

How reproducible:
Always

Steps to Reproduce:
1.have a directory shared from Windows XP for writing
2.open that share through nautilus with the smb:// syntax
2.copy a 4GB+ file there

    

Actual Results:  The transferred file was exactly 4GB on the windows
machine, and thus corrupted

Expected Results:  No corruption

Additional info:

The copy bar quickly went to 99%, and stayed there until the end of
the copy.
Comment 1 István Tóth 2003-11-23 19:55:46 UTC 
I've tried to do the same with the kernel smbfs, it bombs out at 2GB
with an error message (as expected with unpatched 2.4) 

With smbclient, the copy was successful, and also felt much faster.
Comment 2 Alexander Larsson 2004-03-03 16:02:29 UTC 
I verified that this works with fc2 latest gnome-vfs2 copying a
4736116602 byte file to a samba server. It worked fine.
Note You need to log in before you can comment on or make changes to this bug.