Hello all,
I have a foxpro application that someone else wrote that I am trying to
support to XP clients.
I have done what I can to disable oplocks on my end and they are all
service pack 2 XP Professional workstations.
in my [global] section I have the following:
# http://www.drouillard.ca/Tips&Tricks/Samba/Oplocks.htm
lock spin time = 15
lock spin count = 30
kernel oplocks = No
oplocks = No
level2 oplocks = No
veto oplock files = /*.idx/*.dbf/*.cdx/*.fpt/*.IDX/*.DBF/*.CDX/*.FPT/
Not sure if this is useful or not, but the share is on a 3ware raid
(raid-1) on a FreeBSD 6.1 box w/ samba3 from ports.
If anyone can shed some light on this it would really help me.. I've
been trying to make this work for over a week (40+ hours) now; and it
runs ok for a few hours, then smbd gets an error and locks everyone out
of that file.
Until I restart samba.
This is what appears in the logs:
[2006/06/06 13:53:32, 0]
smbd/oplock.c:release_level_2_oplocks_on_change(771)
release_level_2_oplocks_on_change: failed to lock share mode entry
for file data/servmst1.CDX.
[2006/06/06 13:53:32, 0] lib/fault.c:fault_report(36)
==============================================================[2006/06/06
13:53:32, 0] lib/fault.c:fault_report(37)
INTERNAL ERROR: Signal 11 in pid 97478 (3.0.22)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2006/06/06 13:53:32, 0] lib/fault.c:fault_report(39)
From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2006/06/06 13:53:32, 0] lib/fault.c:fault_report(40)
==============================================================[2006/06/06
13:53:32, 0] lib/util.c:smb_panic2(1554)
PANIC: internal error
The box has been up almost 18 hours and smbd has dumped 11 times so far..
I thought it was ram, (so I changed it), powersupply (so I changed it),
motherboard, (changed), cpu (changed) and I still have it..
Please if someone can help or give me something else to look at..
thank you in advance
