at copying of two identical files on a computer with freebsd (samba3.026a, vsftpd) on protolam - Samba and FTP, and subsequent their reading from a cantilever in nul, speed of file of written down Samba in 2 times less, a hard disk is empty, checked up on different hard disks and two computers - FreeBSD7 and FreeBSD6.3
What client are you using? Please try smbclient from 3.2.0rc1, we've improved reading speed significantly in that client prog.
(In reply to comment #1)
> What client are you using? Please try smbclient from 3.2.0rc1, we've improved
> reading speed significantly in that client prog.
I do not use smbclient, I read files straight from a FreeBSD cantilever to /dev/null on computer which Samba server
Reading speed off a samba share very much depends on the exact client behaviour. That's why I said that we have done much work to get the smbclient utility fast.
I am marking this bug as invalid because I assume that the FreeBSD client that you are using is using is using non-optimal requests like sequential 4k reads or so. If smbclient from 3.2.0rc1 is also slow, please re-open this bug with a sniff and a server-side debug level 10 log.
you did not understand me, my problem not in the read rate from a samba resource, but in that if I write down a file by samba, after he is read slower what if would be written down on FTP or another way? difference in the read rate to 2 times....
P.S. I use translator from Russian, if something is not quite clear - will make attempt translate....
Wait a second -- you write a file via Samba the speed reading it from disk after that is 50% slower than if you wrote it via ftp or direct? That is even more weird.
The only explanation would be that the client you are using is writing with a very weird write pattern that causes FreeBSD to heavily fragment the file. There is also not much that Samba as a server can do here. To work around this, you might want to look at the preallocate vfs module.