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.
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).
Robert
:wq!
---------------------------------------------------------------------------
Robert L. Harris | GPG Key ID: E344DA3B
@ x-hkp://pgp.mit.edu
DISCLAIMER:
These are MY OPINIONS ALONE. I speak for no-one else.
With Dreams To Be A King First One Should Be A Man
- Manowar
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url :
http://lists.samba.org/archive/samba/attachments/20040730/94ba3bff/attachment.bin
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 abartlet@samba.org Authentication Developer, Samba Team http://samba.org Student Network Administrator, Hawker College abartlet@hawkerc.net -------------- 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/20040801/8d39c63e/attachment.bin
Sorry, I'm loosing my mind. We have samba-doc 2.0.7-1 but our actual samba version is 2.2.3a-13 (which is why our update system reported it as current.). We stopped samba and cleaned out /var/run/samba and restarted. The oplock_break error messages are gone but my users are saying: ------ Still having intermittent problem with accessing and saving files in the capacity planning drive. It's just frustrating to kept on trying to access and if I'm successful in accessing the file, I'm unable to save the changes. I:\planning\Monthly\July2004.xls Here's the error message: "Entrance-Interconnect.xls cannot be accessed. The file maybe read-only, or you maybe trying to access a read-only location or the server the document is saved on may not be responding." ------ /var/log/* looks clean in general and I can't find any errors samba or system related. The server which NFS exports this filesystem to the Samba server (long story) also is clean of errors. Thoughts? Robert Thus spake Robert L. Harris (Robert.L.Harris@rdlg.net):> > 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. > > 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). > > Robert > > > :wq! > --------------------------------------------------------------------------- > Robert L. Harris | GPG Key ID: E344DA3B > @ x-hkp://pgp.mit.edu > DISCLAIMER: > These are MY OPINIONS ALONE. I speak for no-one else. > > With Dreams To Be A King First One Should Be A Man > - Manowar >:wq! --------------------------------------------------------------------------- Robert L. Harris | GPG Key ID: E344DA3B @ x-hkp://pgp.mit.edu DISCLAIMER: These are MY OPINIONS ALONE. I speak for no-one else. With Dreams To Be A King, First One Should Be A Man - Manowar -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.samba.org/archive/samba/attachments/20040804/c5f7b596/attachment.bin