I currently experiencing very strange errors with filelocking. Long time after a application closed the file, smbstatus still shows the files as locked. Of course if another application is going to write to that file, the error "Text file busy" occurs. Server and client OS: SuSE 9.1 Vanilla kernel 2.6.7-rc3 It seems to be a problem that occurs only with Linux Kernel 2.6.x since it also occurs with samba 2.2.9. I'm going to try to track down when exactly that is going to happen... thanks Luc
Created attachment 546 [details] excerpt from the clients syslog This is a smaller excerpt from the clients syslog.
I'm not sure if the submitted logfile entries have something to do with the file locking/unlocking problem. Please have a look at it.
I have the same problem with 3.0.21: Samba version 3.0.21 PID Username Group Machine ------------------------------------------------------------------- 25122 sstrickroth users 192.168.0.1 (192.168.0.1) 16142 sstrickroth users mrtux (192.168.250.13) 24252 linux users 192.168.0.1 (192.168.0.1) Service pid machine Connected at ------------------------------------------------------- onlinetafel 24252 192.168.0.1 Wed Dec 21 20:11:35 2005 sstrickroth 16142 mrtux Fri Dec 23 07:28:38 2005 sstrickroth 25122 192.168.0.1 Wed Dec 21 20:22:29 2005 Locked files: Pid DenyMode Access R/W Oplock Name -------------------------------------------------------------- 22989 DENY_NONE 0x100001 RDONLY NONE Favoriten/Links Thu Dec 22 08:03:36 2005 24889 DENY_NONE 0x100001 RDONLY NONE Desktop Thu Dec 22 08:00:35 2005 24889 DENY_NONE 0x100001 RDONLY NONE Desktop Thu Dec 22 08:00:35 2005 9596 DENY_NONE 0x100001 RDONLY NONE Desktop Thu Dec 22 12:54:35 2005 9596 DENY_NONE 0x100001 RDONLY NONE Desktop Thu Dec 22 12:54:36 2005 5425 DENY_NONE 0x100001 RDONLY NONE Desktop Thu Dec 22 12:59:59 2005 5425 DENY_NONE 0x100001 RDONLY NONE Desktop Thu Dec 22 12:59:59 2005 9596 DENY_NONE 0x12019f RDWR NONE Cookies/index.dat Thu Dec 22 12:55:02 2005 24889 DENY_NONE 0x12019f RDWR NONE Cookies/index.dat Thu Dec 22 08:00:40 2005 26897 DENY_NONE 0x100001 RDONLY NONE Desktop Thu Dec 22 08:02:10 2005 26897 DENY_NONE 0x100001 RDONLY NONE Desktop Thu Dec 22 08:02:11 2005 5671 DENY_NONE 0x100001 RDONLY NONE Desktop Thu Dec 22 08:09:10 2005 5671 DENY_NONE 0x100001 RDONLY NONE Desktop Thu Dec 22 08:09:11 2005 26897 DENY_NONE 0x12019f RDWR NONE Cookies/index.dat Thu Dec 22 08:02:20 2005 5671 DENY_NONE 0x12019f RDWR NONE Cookies/index.dat Thu Dec 22 08:09:17 2005 22989 DENY_NONE 0x12019f RDWR NONE Cookies/index.dat Thu Dec 22 08:02:06 2005 9596 DENY_NONE 0x100001 RDONLY NONE Favoriten/Links Thu Dec 22 12:58:10 2005 24889 DENY_NONE 0x100001 RDONLY NONE Favoriten/Links Thu Dec 22 08:04:01 2005 22989 DENY_NONE 0x100001 RDONLY NONE Desktop Thu Dec 22 08:02:02 2005 22989 DENY_NONE 0x100001 RDONLY NONE Desktop Thu Dec 22 08:02:02 2005
lock entries are cleaned up by ensuring that the responsible pid still exists and are removed if the parent pid is not running.
Created attachment 2033 [details] smbstatus and ps aux output I don't think so. I've a kernel patched with a randomized-pids-patch.