Well...I havent had such problems before I have upgraded to Sarge;
Now I am checking my network conditions and my clients.
I have put oplock_break_wait_time and since yesterday I have no oplock
errors.
In order not to make you trouble please close this bug until more users
report same situation.
Thanks for response.
Steve Langasek napisał(a):
On Mon, Feb 06, 2006 at 05:05:41PM +0100, Leszek Dubiel wrote:
On 2005-11-11 I have upgraded my system Debian Woody to Debian Sarge. I
can see similar oplock problems in my log files since then as described
in a bug report. This makes our file-database crush every time.
[2006/02/06 07:40:19, 0] smbd/oplock.c:oplock_break(847)
oplock_break: receive_smb timed out after 30 seconds.
oplock_break failed for file FPP/DESCLA.DLL (dev = 301, inode = 939100,
file_id = 91).
[2006/02/06 07:40:19, 0] smbd/oplock.c:oplock_break(919)
oplock_break: client failure in oplock break in file FPP/DESCLA.DLL
[2006/02/06 08:38:05, 0] smbd/oplock.c:oplock_break(847)
oplock_break: receive_smb timed out after 30 seconds.
oplock_break failed for file FPP/FPPINT.DLL (dev = 301, inode = 939097,
file_id = 11).
Breaking an oplock requires the cooperation of the client holding it. Are
you sure this isn't a case of a misbehaving client? Either an oplock held
by a hung client, or high packet loss on your network, could cause such a
problem.
|
