Prev: Samsung ML-1610
Next: PAM
From: Henrik Carlqvist on 8 Mar 2006 16:59
"CL" <cl(a)screamx.com> wrote:
>> First of all, to really make sure what kind of file system you are tring
>> to use and what limitations you have, please provide the following info:
>>
>> uname -r
>> mount

> I am indeed mounted an smb network file system.
> Below is the info.

> uname -r
> 2.4.26
>
> mount
> /dev/hda3 on /home type ext2 (rw)
> //myserver/back on /mnt/myserver type smbfs (0)
>
> I copy from /home to /mnt/myserver.
>
> Anyway, thank for your advise.

Ok, things are becoming more clear now. You are copying to an smb network
file system. I know that there is a limit of 2 GB with kernel 2.4.22 which
was shipped with Slackware 9.1 when mounting an SMB file system and I know
that limit is gone with kernel 2.4.31 which ships with Slackware 10.2.
However, I don't know about kernel 2.4.26, if the limitation is still
there. You got me a little bit confused as you have kernel 2.4.26, did you
upgrade to that kernel yourself? In an earlier post you said that you were
running Slackware 8.1 which comes with kernel 2.4.18.

In one of your later posts it also seemed as if the problem went away when
you used NTFS. Did you by that mean that your windows file server is
running FAT32 when you have the problem? In another message you wrote it
seemed as if you had the problem when the server had NTFS? In that message
you also wrote that the file size was about 3.6 GB. Even if the server had
FAT32 it should be able to handle a 3.6 GB file as FAT32 is supposed to
handle files up to 4 GB.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc8(at)uthyres.com Examples of addresses which go to spammers:
root(a)variousus.net root(a)localhost

First  |  Prev  | 
Pages: 1 2 3 4 5
Prev: Samsung ML-1610
Next: PAM