Joined: Sep. 2005
||Posted: Aug. 15 2008,09:13
Well, we are suggesting things because we don't know for sure. This isn't kernel hacker central y'know.
And Serge, it will help if you tell us the outcome of trying things we have suggested. You haven't done that. Did you remount your Samba share using the -o lfs option? You haven't said.
System limitations: process and resource limits that the system knows about can be seen and re-set with the ulimit command.
Can you please post the output of the following commands:
|Code Sample |
| # sysctl -a | grep net.ipv4.tcp_mem |
I think the most likely thing though, as had been suggested, is that something has been compiled without large file support and it's never come up before for some reason.
Have you tried moving the file without samba? You haven't said. For example, running monkeyserver on dsl and downloading it via your browser on the other machine, or by ftp? That would tell us whether samba is the culprit or not.