The general consensus on the web/usenet (etc) is to turn on the
use_sendfile=NO option in vsftpd.conf, but this would only save the
first write after any restart of the vsftpd service. The actual
solution came from mounting the directories with the mount.cifs option
"nobrl" which configures the kernel such that it does not send byte
range lock requests to the server. Or something.
use_sendfile=NO did however have a use in preventing "426 Failure
writing network stream." on ftp reads.
The entire mount commands were:
mount -t cifs -o credentials=/etc/samba/cifs_credentials -o rw -o
nobrl //Win2003SR2/ftp$/inbound /var/ftp/inbound
mount -t cifs -o credentials=/etc/samba/cifs_credentials -o rw -o
nobrl //Win2003SR2/ftp$/outbound /var/ftp/outbound
packages in use (not necessarily relevant):
samba-client-3.0.25b-1.el5_1.4
samba-common-3.0.25b-1.el5_1.4
kernel-xen-2.6.18-53.1.6.el5
vsftpd-2.0.5-10.el5
Hope this helps.
I would have liked to have the same situation to try your solution...
the environment is dead now though...