samba - Oct 2006 - Office: File currently in use by user xyz problem!

Hi,

today we got some mysterious errors.. a machine was hard reset and after 
the boot this user tried to re-open a file previously opened with full 
read/write access. This failed, many previously opened files were locked 
due to "currently n use by user xyz" problems, which were different 
usernames though these users -as word/excel claimed- didn't have these 
files open at that time. Couldn't even see these files locked via smbstatus.

I veto disabled oplocks before on office files..
Now I also disabled level2 oplocks globally, if that could be a factor.

Does anyone know what could be causing these problems?

Thnx a lot for any help.

On Fri, Oct 06, 2006 at 02:27:09PM +0200, Michael Rignaz
wrote:
> today we got some mysterious errors.. a machine was hard reset and after 
> the boot this user tried to re-open a file previously opened with full 
> read/write access. This failed, many previously opened files were locked 
> due to "currently n use by user xyz" problems, which were
different
> usernames though these users -as word/excel claimed- didn't have these 
> files open at that time. Couldn't even see these files locked via
smbstatus.
Which Samba version are you using? If you have multiple
installations of Samba on your machine, are you sure you are
using the correct smbstatus binary?
> I veto disabled oplocks before on office files..
> Now I also disabled level2 oplocks globally, if that could be a factor.
It is highly unlikely that oplocks have anything to do with
your problem.

In your case setting 'reset on zero vc = yes' might help.
Please read the manpage for smb.conf for possible caveats
with this parameter.

Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://lists.samba.org/archive/samba/attachments/20061006/91110b8e/attachment.bin

Sorry for the extrapost, too retarded when I'm lacking sleep... forgot 
to attack the smb.conf and to tell that the problem was resolved when 
restarting the samba daemons!

running samba 3.0.23c-1

    workgroup = xyz

passwd chat = *New*Password* %n\n*Re-enter*new*password* %n\n 
*Password*changed*
username map = /etc/samba/smbusers

    server string = %h server (Samba %v)
    wins support = yes
    time server = Yes

    dns proxy = no
    name resolve order = wins lmhosts host bcast
    interfaces = 192.168.0.0/24 eth0 127.0.0.0/8 lo
	bind interfaces only = true
    log file = /var/log/samba/log.%m
    max log size = 10000
    log level = 2
    syslog = 0
    security = user
    encrypt passwords = true
    passdb backend = tdbsam

    obey pam restrictions = yes
    unix password sync = Yes
    domain logons = yes
    preferred master = yes

    utmp = Yes
    map acl inherit = Yes
    hide files = /.*/desktop.ini/
    oplocks = False
    level2 oplocks = False
    logon path = \\%N\profiles\%U
    logon drive = z:
    logon home = \\%N\%U
    logon script = logon.cmd
    printing = cups
    printcap name = cups
add user script = /usr/sbin/useradd -m '%u'
delete user script = /usr/sbin/userdel -r '%u'
add group script = /usr/sbin/groupadd '%g'
delete group script = /usr/sbin/groupdel '%g'
add user to group script = /usr/sbin/usermod -G '%g' '%u'
add machine script = /usr/sbin/useradd -s /bin/false -d /var/lib/nobody
'%u'


socket options = TCP_NODELAY  SO_RCVBUF=8192 SO_SNDBUF=8192
domain master = auto


#####now come the shares... posting only the relevant one..#####

[Share where these problems occured]
    comment     path = /smb/...
    writeable = no
    write list = @somegroup
    force group = somegroup
    create mask = 0770
    directory mask = 0770


thnx a lot!