I'm having a problem involving Outlook and .pst files and a lock that is getting "stuck" I believe. Once Outlook crashes in the fashion it does, it is unable to reopen the file, claiming it is already in use. Explorer also does not let me access the file. Rebooting the workstation does not fix it. smbstatus does not show the lock, however hwen I show byte range locks, there is one, from a PID that doesn't exist. I assume this is the problem lock. The smbd that owned the lock died when the client rebooted/reconnected. I am unable to fix this problem. I think that samba at least needs a smblocks utility to force locks to be released, and manipulate the lock db (is there such a thing) in order to fix solutions like these. When it happens a user on the network is unable to access their email until samba is restarted, which cannot be done during normal working hours... it's becoming a big problem. (does it already have such a utility?) I am using 3.0.3pre1, Debian Woody. Linux 2.4.22. Thanks. Jerry Haltom -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.samba.org/archive/samba/attachments/20040305/ff24a75f/attachment.bin
<quote> I'm having a problem involving Outlook and .pst files and a lock that is getting "stuck" I believe. Once Outlook crashes in the fashion it does, it is unable to reopen the file, claiming it is already in use. Explorer also does not let me access the file. Rebooting the workstation does not fix it. smbstatus does not show the lock, however hwen I show byte range locks, there is one, from a PID that doesn't exist. I assume this is the problem lock. </quote> Hello! We had completely the same problem with samba 3.0.0, so we downgraded it back to 2.2.8. I wrote about this problem, but nobody else said that they have such problem... Yesterday I installed 3.0.2a in fileserver. Looks like I'll have to downgrade it again, if problem is still exists :-( Unfortunately, I can't reproduce this problem on test server.. btw, we run SLES8. <quote> I think that samba at least needs a smblocks utility to force locks to be released </quote> I think this is good idea. And, I need the same tool for WINS database too ;-)