On Sat, 2004-07-31 at 06:20, Robert L. Harris wrote:
Recently a production stable samba server started producing this:
samba-log.cpr8r: oplock_break failed for file Share1/Files/Financial/Comms.xls (dev
= b, inode = 151073815, file_id = 31).
samba-log.cpr8r: oplock_break failed for file Share1/Files/Financial/Futures.xls
(dev = b, inode = 411546895, file_id = 31).
samba-log.cpr8r: oplock_break failed for file Share1/Files/Financial/Historical.xls
(dev = b, inode = 402910038, file_id = 8).
etc etc for many many files. My samba logs currently give this 580
times in the last 2 days since the server was restarted.
This is due to the client failing to acknowledge the Oplock break
(usually).
The closest match is on google from 1999 and there's no reply.
Samba.org doesn't even have any matches on their search page I can find.
Anyone have any ideas what could cause this?
Kernel 2.4.26-bk1
Samba 2.0.7-1
Debian Stable
The hardware is a P3-850 with 512Megs of ram.
Most of the files being accessed are nfs mounted from a hardare
appliance (SNAP).
If possible, you should use the version of Samba on the SNAP appliance.
Samba backed by NFS is not a good idea - you probably only get away with
it due to the age of your Samba installation.
Samba 2.0.7 has known security holes, and should be upgraded to current
3.0.
Depending on which SNAP appliance you have, you may be able to purchase
an OS upgrade (to the Linux/Samba 3.0 based version).
Andrew Bartlett
--
Andrew Bartlett [EMAIL PROTECTED]
Authentication Developer, Samba Teamhttp://samba.org
Student Network Administrator, Hawker College [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
