Problems displaying large files on

[Dragos]

you seem to have quite a problem here...I'm out of my knowledge.
I thought it was related to stat, I had some problems on a server with it, bu 
it wasn't a samba server.
just a thought: be sure that you haven't an older version of stat on the 
system, like you have it in your path as root, and samba finds in it's path 
something else...
also, take a look at the logs while you're browsing the share, the message 
can't stat blahblah... shouldn't appear anymore
also, see the output from ./configure I get on samba 2.2.2 sources:
...
checking checking if large file support can be enabled... yes
...
verify yours (it's about the end, before generating makefiles)

good luck
dragos

On Monday 15 October 2001 10:37 pm, Ivan Fernandez wrote:
> Hi again,
>
> 	after a new clean compilation of samba 2.2.2 with glibc 2.2.4 as linking
> library over a  kernel 2.4.9 I keep on having problems reading files larger
> than 2 Gb (exactly) through my samba shares.
>
> stat says the following:
>
> pokeball:/backup1# stat casi.bkf
>   File: "casi.bkf"
>   Size: 3827375104      Blocks: 7475344    IO Block: 4096   Regular File
> Device: 1601h/5633d     Inode: 5           Links: 1
> Access: (0764/-rwxrw-r--)  Uid: ( 1008/   admin)   Gid: ( 1008/   admin)
> Access: Mon Oct 15 16:38:37 2001
> Modify: Sat Oct 13 15:13:57 2001
> Change: Sat Oct 13 15:19:39 2001
>
> ls -l also lists size ok:
>
> -rwxrw-r--    1 admin    admin    3827375104 Oct 13 15:13 casi.bkf
>
>
> but, programs like mc raise up with an error saying the file can't be
> stated, and windows machines cannot even see the file (though they list the
> share with 3,6 G occupied)
>
> The funniest thing is that with samba 2.2.1a from debian's package I saw
> files on the share no matter the length they had. I copied a 22G file from
> my windows harddisk to the samba share without problems, but I couldn't
> (and here started it all) use ntbackup to directly generate that 22G file
> over the share... Any other idea will be appreciated
>
> Have fun! :-) (it's time to party after a whole day lost with this little
> detail :(  )