Samba file copy maximum of 2 GB?

dcroxton · 02-06-2007, 05:52 PM

I'm having a problem copying a file of > 2 GB onto a Samba share.

Here's the setup:

An external hard drive with a reiserfs partition of c.150 GB (running on Xandros 2.5)
Above partition set up as a samba share, which I am using from an Ubuntu Edgy client.
Copying files from the client to the samba share of > 2 GB always stops at exactly 2 GB and says the transfer was terminated unexpectedly. (I'm using Krusader for transfers.)

I haven't seen anything about a 2 GB limit on Samba on the web, although I did see something about a 4 GB limit (which would also be a problem, though I didn't see how to change it). The closest thing I can find to an error is the following from the samba log on the Xandros box:

Code:

[2007/02/06 17:13:43, 0] lib/util_sock.c:read_data(526)
  read_data: read failure for 4 bytes to client 192.168.2.5. Error = Connection 
reset by peer

I tried using Krusader's ability to split a file and recombine it. This successfully transferred the file, but when I tried to recombine it, it also crashed after building a 2 GB file! This experience suggests that maybe it's a reiserfs problem, but I haven't seem anything about that.

The strangest thing is that I actually have files in this directory of > 5 GB, which I know I must have transferred from the Ubuntu box. Which suggests that neither reiserfs nor samba is the problem.

I can think of a couple of workarounds: try the transfer using ftp, or export the partition using nfs. The latter isn't really an option because I want it to be accessible to Windows computers on my network. The former is possible (I haven't tried yet) but a pain.

Any idea why I'm running into this limit??

Micro420 · 02-07-2007, 04:47 PM

Not sure if there are limitations, but can you just use scp or sftp to temporarily transfer it over? Make sure there is enough hard drive space on the client.

dcroxton · 02-12-2007, 09:51 AM

Yes, I probably could do that (and I will try). I was just hoping for a more regular solution, integrated into my file manager (plus, of course, the fact that it doesn't work makes me want to fix it).

zytsef · 02-12-2007, 10:29 AM

I sort of doubt that it's a samba problem. You could try mounting the partition with smbmnt to try to figure out if it really is samba. You say it's an external drive, I would try transfering a large file on to it from a local machine and see if it isn't something strange happening with the partition.

pdown85 · 02-12-2007, 05:41 PM

Quote:

Originally Posted by dcroxton

I'm having a problem copying a file of > 2 GB onto a Samba share.

Here's the setup:

An external hard drive with a reiserfs partition of c.150 GB (running on Xandros 2.5)
Above partition set up as a samba share, which I am using from an Ubuntu Edgy client.
Copying files from the client to the samba share of > 2 GB always stops at exactly 2 GB and says the transfer was terminated unexpectedly. (I'm using Krusader for transfers.)

I haven't seen anything about a 2 GB limit on Samba on the web, although I did see something about a 4 GB limit (which would also be a problem, though I didn't see how to change it). The closest thing I can find to an error is the following from the samba log on the Xandros box
...
Any idea why I'm running into this limit??

What's the paritioning on your Samba drive?
The maximum file size on a FAT32 formatted partition is 4 GB.
The maximum file size on a FAT16 partition is 2GB.
Could this be the problem - rather than a Samba issue a partitioning issue?

XaViaR · 02-13-2007, 12:31 PM

Dunno if this will help ya. I found this last week when I was having the same trouble. BUT, I am using Redhat.

http://kbase.redhat.com/faq/FAQ_71_4536.shtm

Good luck!

dcroxton · 02-13-2007, 02:52 PM

Quote:

Originally Posted by XaViaR

Dunno if this will help ya. I found this last week when I was having the same trouble. BUT, I am using Redhat.

http://kbase.redhat.com/faq/FAQ_71_4536.shtm

Good luck!

Problem solved! Thank you. The external drive is formatted Reiserfs, so I was pretty sure that wasn't the problem. (That, and the fact that I actually have files > 2 GB on it already.) Passing the lfs option made it work.

Thanks to everyone for your input.