From owner-freebsd-questions Thu Sep 20 13:31:18 2001 Delivered-To: freebsd-questions@freebsd.org Received: from benny.geektank.org (00-04-ac-38-0e-e8.bconnected.net [209.53.63.19]) by hub.freebsd.org (Postfix) with ESMTP id 8188B37B40B for ; Thu, 20 Sep 2001 13:31:15 -0700 (PDT) Received: from localhost (tmchow@localhost) by benny.geektank.org (8.11.6/8.11.6) with ESMTP id f8KKV4o50422 for ; Thu, 20 Sep 2001 13:31:04 -0700 (PDT) (envelope-from tmchow@sfu.ca) Date: Thu, 20 Sep 2001 13:31:04 -0700 (PDT) From: Trevin Chow X-X-Sender: To: Subject: re: Flaky samba server Message-ID: <20010920132912.W50413-100000@benny.geektank.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Okay, here's my follow-up on my flaky samba performance. Around the time that the server seems to disconnect them suddenly reconnect, I examined the logs (at logging level = 2): [2001/09/20 13:21:37, 2] smbd/open.c:open_file(216) tmchow opened file test-dir/test.gif read=Yes write=Yes (numopen=2) [2001/09/20 13:21:37, 2] smbd/process.c:switch_message(661) switch_message: queueing message due to being in oplock break state. [2001/09/20 13:21:39, 2] smbd/process.c:switch_message(661) switch_message: queueing message due to being in oplock break state. [2001/09/20 13:21:42, 2] smbd/process.c:switch_message(661) switch_message: queueing message due to being in oplock break state. [2001/09/20 13:22:06, 2] smbd/process.c:switch_message(661) switch_message: queueing message due to being in oplock break state. [2001/09/20 13:22:37, 0] smbd/oplock.c:oplock_break(770) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file test-dir/test.gif (dev = 27407, inode = 531718). [2001/09/20 13:22:37, 0] smbd/oplock.c:oplock_break(843) oplock_break: client failure in oplock break in file test-dir/test.gif [2001/09/20 13:22:37, 2] smbd/open.c:open_file(216) tmchow opened file test-dir/test.gif read=Yes write=No (numopen=3) [2001/09/20 13:22:37, 0] smbd/reply.c:reply_lockingX(4393) reply_lockingX: Error : oplock break from client for fnum = 8296 and no oplock granted on this file (test-dir/test.gif). Does this indicate any problems that can be fixed? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message