
I am running a machine with RH 7.1, samba-2.0.10 I moving some large files from a Windows XP machine to the large amount of diskspace that is available ont he Linux machine. Files that are larger than 4GB fail to copy. Once the progress reaches 4GB windows prompts you if you wish to overright the exisiting file. I am already planning on installing a newer release on the linux box, probably Fedora Code 3 (or 4, as It will probably be out by the time I get around to it). I would like to know if any of you have successfully copied files larger than 4GB from a Windows machine to a recent build on samba. I'm not sure if it's Samba, Windows XP or the SMB protocol that is limited at 4GB. I realy don't care either, but I would like to know if this will work, it might motivate me to upgrade a little faster ;-) Anyone with FC3 able to confirm that this has worked. Raymond

On Tue, Apr 05, 2005 at 01:57:51PM +1000, Raymond Burgess wrote:
I would like to know if any of you have successfully copied files larger than 4GB from a Windows machine to a recent build on samba. I'm not sure if it's Samba, Windows XP or the SMB protocol that is limited at 4GB. I realy don't care either, but I would like to know if this will work, it might motivate me to upgrade a little faster ;-)
It's probably due to an old kernel causing the file size limit. Upgrading is a good idea ;) Perhaps even exploring different distributions?

James Clark wrote:
On Tue, Apr 05, 2005 at 01:57:51PM +1000, Raymond Burgess wrote:
I would like to know if any of you have successfully copied files larger than 4GB from a Windows machine to a recent build on samba. I'm not sure if it's Samba, Windows XP or the SMB protocol that is limited at 4GB. I realy don't care either, but I would like to know if this will work, it might motivate me to upgrade a little faster ;-)
It's probably due to an old kernel causing the file size limit.
I doubt FC3 is running a kernel that old (2.2.x?!), and the Linux filesystem limit was 2G, not 4G, as Linux uses off_t which because of llseek() requirements needs to be signed thus making it 2G. Windows doesn't use llseek() the same way, and thus they are limited to 4G. I'd suggest that this is somewhere in the SMB protocol, Windows, or samba's implementation of the SMB protocol.

On Tue, Apr 05, 2005 at 04:57:36PM +1200, Perry Lorier wrote:
It's probably due to an old kernel causing the file size limit.
I doubt FC3 is running a kernel that old (2.2.x?!), and the Linux
Unless I got my wires crossed, he said "I am running a machine with RH 7.1, samba-2.0.10" and was considering going to FC3. I'm probably wrong about the cause, but if he's running (very) old software it's time to upgrade. James.

On Tue, Apr 05, 2005 at 04:57:36PM +1200, Perry Lorier wrote:
It's probably due to an old kernel causing the file size limit.
I doubt FC3 is running a kernel that old (2.2.x?!), and the Linux
Unless I got my wires crossed, he said "I am running a machine with RH 7.1, samba-2.0.10" and was considering going to FC3.
I'm probably wrong about the cause, but if he's running (very) old software it's time to upgrade.
James.
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug -- Oliver Jones » Roving Code Warrior
The old kernel on the RH7.1 box could well be the issue too. Something in the equation is using a signed 32 bit integer for the file size limit. Newer Linux kernels and file systems don't have this problem. Regards On Tue, 2005-04-05 at 17:30 +1200, James Clark wrote: oliver(a)deeperdesign.com » +64 (21) 41 2238 » www.deeperdesign.com

On Tue, 2005-04-05 at 13:57 +1000, Raymond Burgess wrote:
I am running a machine with RH 7.1, samba-2.0.10
And I thought hostility was old running 7.3 ;)
Files that are larger than 4GB fail to copy. Once the progress reaches 4GB windows prompts you if you wish to overright the exisiting file.
I would like to know if any of you have successfully copied files larger than 4GB from a Windows machine to a recent build on samba. I'm not sure if it's Samba, Windows XP or the SMB protocol that is limited at 4GB. I realy don't care either, but I would like to know if this will work, it might motivate me to upgrade a little faster ;-)
I've had the same problem before. I believe it is Samba that is at fault. Ext3 can support files larger than 2GB. I think it can do files up to several terabytes in size. And NTFS certainly can do huge files. Samba 2.x seems to be using 32 bit file offsets though. Which sucks. Use RAR to split the file on the Windows XP box (use a target file on the Linux box if there is no room on the XP machine for the RARs. Then unrar it on the Linux box. If you have Cygwin installed you can use split to do the same job. But then you new this already. :) Regards -- Oliver Jones » Roving Code Warrior oliver(a)deeperdesign.com » +64 (21) 41 2238 » www.deeperdesign.com

I've had the same problem before. I believe it is Samba that is at fault. Ext3 can support files larger than 2GB. I think it can do files
So does ext2 as it happens, it's the 2.2 kernel which has issues. And if your distribution is built with a 2.2 kernel in mind, your entire userspace will suffer from the same issue. Vis-a-vis Debian Woody, which ships with 2.2.19 as the default kernel. You can use 2.4.18 straight from install, but getting 64bit file offset support is a royal pain in the ass.

Raymond Burgess wrote:
I am running a machine with RH 7.1, samba-2.0.10
I moving some large files from a Windows XP machine to the large amount of diskspace that is available ont he Linux machine.
Files that are larger than 4GB fail to copy. Once the progress reaches 4GB windows prompts you if you wish to overright the exisiting file.
I am already planning on installing a newer release on the linux box, probably Fedora Code 3 (or 4, as It will probably be out by the time I get around to it).
I would like to know if any of you have successfully copied files larger than 4GB from a Windows machine to a recent build on samba. I'm not sure if it's Samba, Windows XP or the SMB protocol that is limited at 4GB. I realy don't care either, but I would like to know if this will work, it might motivate me to upgrade a little faster ;-)
Anyone with FC3 able to confirm that this has worked.
Have you considered using pscp from http://www.chiark.greenend.org.uk/~sgtatham/putty/ I have found the putty suite to be very useful under windows and doing an scp transfer should get around any possible issues with samba and at least narrow down the possible cause of the problem if it still fails.

Have you considered using pscp from http://www.chiark.greenend.org.uk/~sgtatham/putty/ I have found the putty suite to be very useful under windows and doing an scp transfer should get around any possible issues with samba and at least narrow down the possible cause of the problem if it still fails.
On a side note, pscp is god awful slow - feels like half the speed of Linux scp, and of course these are both slower than smb due to the encryption overhead. Useful, sure, but very slow. WinSCP is no better as it uses PuTTY's encryption code. Craig
participants (7)
-
Craig Box
-
Daniel Lawson
-
James Clark
-
Jason Drake
-
Oliver Jones
-
Perry Lorier
-
Raymond Burgess