Hello I have got a problem coping files from win xp machines to samba. When I try to copy file about 10 MB, it copies 100% but then the progress window does not disaapear, still showing 100% and after about 1 minute win xp says "coping not sucessfull - hardware error or network connection error" When i try to copy the same file from win2000 pc everything is ok. The samba log says * Existent* *process* 20445 *left* *active* *oplock **no* *response* *received* to *oplock* *break and *so i put to my smb.conf kernel oplocks = no and level2 oplock = no but it is still the same any ideas?
any ideas? Check this option in /etc/samba/ smb.conf use sendfile = No|Yes try to switch it. The current state you can see by using testparm -v | grep sendfile -- Best regards Alexandr R. Ogurtzoff { UNIX is user friendly, it's just picky about who its friends are }
On Wednesday 08 December 2004 12:35 pm, Alexandr R. Ogurtzoff wrote:
any ideas? Check this option in /etc/samba/ smb.conf use sendfile = No|Yes try to switch it. The current state you can see by using testparm -v | grep sendfile
There seems to be a bug in SWAT, the Samba configuration program. If you change the "use sendfile" setting, the change doesn't show up in smb.conf. It doesn't matter whether you change it to Yes or No. The only way to effectively change the setting is to modify smb.conf. I haven't checked if Yast does any better than Swat. Paul
effectively change the setting is to modify smb.conf. I haven't checked if Yast does any better than Swat. I'm nothing to say about SWAT. I wrote my smb.conf just by /dev/head | /dev/hands > vim :-) Manualy I mean. -- Best regards Alexandr R. Ogurtzoff { UNIX is user friendly, it's just picky about who its friends are }
Paul W. Abrahams wrote:
On Wednesday 08 December 2004 12:35 pm, Alexandr R. Ogurtzoff wrote:
any ideas?
Check this option in /etc/samba/ smb.conf use sendfile = No|Yes try to switch it. The current state you can see by using testparm -v | grep sendfile
There seems to be a bug in SWAT, the Samba configuration program. If you change the "use sendfile" setting, the change doesn't show up in smb.conf. It doesn't matter whether you change it to Yes or No. The only way to effectively change the setting is to modify smb.conf. I haven't checked if Yast does any better than Swat.
Even when I was using Red Hat, I found that SWAT didn't work all that well. I just found it easier to configure smb.conf manually.
Thanks for your answer, but when I changed use sendfile to yes it is still the same. I tried to copy file 24 MB of size and the coping stopped in 36%. Win XP said the same error as before and in samba log is Dec 9 11:36:31 backup sshd[3747]: Accepted keyboard-interactive/pam for root from ::ffff:192.168.4.80 port 3154 ssh2 Dec 9 11:44:19 backup smbd[3814]: [2004/12/09 11:44:19, 0] smbd/oplock.c:request_oplock_break(1023) Dec 9 11:44:19 backup smbd[3814]: request_oplock_break: no response received to oplock break request to pid 3813 on port 32768 for dev = 303, inode = 7, file_id = 5 Dec 9 11:44:19 backup smbd[3814]: [2004/12/09 11:44:19, 0] smbd/open.c:open_mode_check(681) Dec 9 11:44:19 backup smbd[3814]: open_mode_check: exlusive oplock left by process 3813 after break ! For file dotnetfx.exe, dev = 303, inode = 7. Deleting it to continue... Dec 9 11:44:19 backup smbd[3814]: [2004/12/09 11:44:19, 0] smbd/open.c:open_mode_check(685) Dec 9 11:44:19 backup smbd[3814]: open_mode_check: Existent process 3813 left active oplock. Alexandr R. Ogurtzoff napsal(a):
any ideas?
Check this option in /etc/samba/ smb.conf use sendfile = No|Yes try to switch it. The current state you can see by using testparm -v | grep sendfile
On Thursday 09 December 2004 11:53, Jan West wrote:
Thanks for your answer, but when I changed use sendfile to yes it is still the same. I tried to copy file 24 MB of size and the coping stopped in 36%. Win XP said the same error as before and in samba log is Something with oplocks. I check my system for this options/ The results are: testparm -v | grep lock Load smb config files from /etc/samba/smb.conf Processing section "[netlogon]" Processing section "[homes]" Loaded services file OK. Server role: ROLE_DOMAIN_PDC Press enter to see a dump of your service definitions
kernel oplocks = Yes lock spin count = 3 lock spin time = 10 oplock break wait time = 0 lock directory = /var/lib/samba block size = 1024 veto oplock files = blocking locks = Yes fake oplocks = No locking = Yes oplocks = Yes level2 oplocks = Yes oplock contention limit = 2 posix locking = Yes strict locking = Yes Are you using Samba from distro or made you own from sources? In 9.1 SuSE, which I use it is Version 3.0.2a-SUSE and it works. -- Best regards Alexandr R. Ogurtzoff { UNIX is user friendly, it's just picky about who its friends are }
participants (4)
-
Alexandr R. Ogurtzoff -
James Knott -
Jan West -
Paul W. Abrahams