samba - May 2008 - MBoyle@ttcdas.com - Email found in subject - RE: Files over 4GB not listing properly. Cannot getCIFSworking.

The default smbclient doesn't list the files properly either.  I've been
romping through the configure script, 
and it turns out that certain flags weren't being properly set in
config.h, due to the fact that samba was
being cross-compiled and the test programs couldn't be run.  So far,
I've set dev_t to be a u_quad type, and
enabled 64-bit versions of: dirent, ino, off_t, SMB_STRUCT_DIR, flock,
and SMB_F_SETLKW/GETLKW.  Is there 
anything i missed?

-----Original Message-----
From: Andrew Bartlett [mailto:abartlet@samba.org] 
Sent: Tuesday, May 06, 2008 7:38 PM
To: Matt Boyle
Cc: samba@lists.samba.org
Subject: MBoyle@ttcdas.com - Email found in subject - RE: [Samba] Files
over 4GB not listing properly. Cannot getCIFSworking.

On Tue, 2008-05-06 at 11:07 -0400, Matt Boyle wrote:
> Put this in the wrong thread, sorry!
> 
> 
> UPDATE:  I've realized that this seems to be an issue with the
compiler flags used to build samba.
> I've realized that i need to define _LARGEFILE_SOURCE,
_LARGEFILE64_SOURCE, and _FILE_OFFSET_BITS=64.
> 
> I've done this, but still have no luck reading files larger than 4GB.
Anyone have suggestions?

smbfs the in-kernel filesystem, (particularly old versions such as in
Linux 2.4) never did files over 4GB well.  

'Fixing' the userspace samba won't change the in-kernel limitations.
I
suggest you find a different way to move the files, perhaps use
smbclient - the default compile should be perfectly fine for large files
(Samba itself has done large files for many years).

Andrew Bartlett

--
Andrew Bartlett
http://samba.org/~abartlet/
Authentication Developer, Samba Team           http://samba.org
Samba Developer, Red Hat Inc.

***Teletronics Technology Corporation*** 
This e-mail is confidential and may also be privileged.  If you are not the
addressee or authorized by the addressee to receive this e-mail, you may not
disclose, copy, distribute, or use this e-mail. If you have received this e-mail
in error, please notify the sender immediately by reply e-mail or by telephone
at 267-352-2020 and destroy this message and any copies.  Thank you.

*******************************************************************