Very Computer

I did an upgrade from Caldera OpenLinux 2.3 to 3.1 using the update
option.
The kernel is 2.4.2.

A Windows 2000 client attempted to copy a file using the Windows
Explorer from a local drive to a Samba shared drive. The file was
approximately 3.0 GB in size. After copying 2.0 GB, the Windows explorer

reported that the connection was lost to the Linux Samba server. The
Windows 2000 client is using NTFS. The Linux drives are e2fs on a 30 GB
SCSI hard drive. There was 9 GB of free space remaining on the target
hard drive.

The client then tried to use SmartFTP to copy the same file to the same
directory. The result was the same. The FTP client reported that the FTP

server had dropped the connection after moving exactly 2.0 GB of data.

The Caldera OpenLinux 3.1 White Paper states that the file size
limitation is 1.0 TB, but this appears not to be true. We upgraded to
Caldera OpenLinux 3.1 just for that purpose, but I don't see performance
as
advertised.

I upgraded the kernel to version 2.4.14 after this and tested one more
time, but
I got the same results.

I tried on another machine with the same Caldera OpenLinux upgraded in
the same
manner. I had a FAT32 partition with a 3.0 GB file on it. I mounted the
partition with
Linux and copied the file using the cp command from the FAT32 partition
to a e2fs
Linux partition. The copy went flawlessly.

Are there limitations on Samba and the ftp server that comes with
Caldera OpenLinux
3.1? Are there limitations with any other Linux Distributions, such as
RddHat?

Thanks,

Larry Irons

Quote:> Linux and copied the file using the cp command from the FAT32 partition
> to a e2fs Linux partition. The copy went flawlessly.

And the resulting copy produced a 3GB file?

--

Software Developer, Engineering Services
Red Hat, Inc.

QUIPd 1.00: (521 of 533)
-> Technology means the systematic application of scientific or
-> other organized knowledge to practical tasks.
-> - John Kenneth Galbraith

Quote:>I did an upgrade from Caldera OpenLinux 2.3 to 3.1 using the update
>option.
>The kernel is 2.4.2.

>A Windows 2000 client attempted to copy a file using the Windows
>Explorer from a local drive to a Samba shared drive. The file was
>approximately 3.0 GB in size. After copying 2.0 GB, the Windows explorer
>reported that the connection was lost to the Linux Samba server. The
>Windows 2000 client is using NTFS. The Linux drives are e2fs on a 30 GB
>SCSI hard drive. There was 9 GB of free space remaining on the target
>hard drive.

>The client then tried to use SmartFTP to copy the same file to the same
>directory. The result was the same. The FTP client reported that the FTP
>server had dropped the connection after moving exactly 2.0 GB of data.

>The Caldera OpenLinux 3.1 White Paper states that the file size
>limitation is 1.0 TB, but this appears not to be true. We upgraded to
>Caldera OpenLinux 3.1 just for that purpose, but I don't see performance
>as advertised.

>I upgraded the kernel to version 2.4.14 after this and tested one more
>time, but I got the same results.

>I tried on another machine with the same Caldera OpenLinux upgraded in
>the same manner. I had a FAT32 partition with a 3.0 GB file on it. I mounted
>the partition with
>Linux and copied the file using the cp command from the FAT32 partition
>to a e2fs
>Linux partition. The copy went flawlessly.

>Are there limitations on Samba and the ftp server that comes with
>Caldera OpenLinux
>3.1? Are there limitations with any other Linux Distributions, such as
>RddHat?

Check out this URL

http://www.suse.de/~aj/linux_lfs.html

It's quite long {18 pages}, but essentially it states that NFSv2 & smbfs
don't support LFS {Large File Support}. Which is why copying a 3 gig file
over Samba won't work.

Also, AFAIK, there's a limitation in the ext2 filesystem which may cause some
problems with older implementations. YMMV.

I don't know why the attempte ftp failed, but I suspect it's for a similar
reason - 2 gigabytes is the maximum filesize allowed by a 32 bit array, which
most of these programs are written for. It's quite possible that your ftp
server isn't compiled/written to accept the 64 bit filesize limits, and
hence the timeout/disconnection.

Samba 2.0.7 apparently supports LFS, but disables them on Linux - which means
you're stuck at 2 gig. Depending on how good a programmer you are, you could
hack the source and see if you can enable them - but that's up to you, 'cause
I sure as hell couldn't do it. :-)

Same deal with your ftp server - you could grab the source, and see if it
can be made to support LFS. Or switch to another FTp server that does support
LFS - maybe ProFTP does - not sure of that one.

Essentially, you're currently fsck'd, unless you can do one of the above.

DaZZa

--
Address in header is spamblocked. ROT13 the following for email replies

This  sounds like the 2GB limit in Solaris. since off_t used for
lseek() is a 4 byte signed integer, the biggest file is 2 GB ( 2**31 =
2GB ).

My linux 2.4.14 gave sizeof( off_t) as 4. So I m expecting the exact
problem in Linux also.

Can somebody pl confirm/comment.

--sony