From owner-freebsd-stable@FreeBSD.ORG Mon Oct 6 14:25:28 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7543B1065687 for ; Mon, 6 Oct 2008 14:25:28 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from mainframe.kkip.pl (kkip.pl [87.105.164.78]) by mx1.freebsd.org (Postfix) with ESMTP id 2707D8FC15 for ; Mon, 6 Oct 2008 14:25:28 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from [192.168.0.10] by mainframe.kkip.pl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Kmr1U-000BIH-Ci for freebsd-stable@freebsd.org; Mon, 06 Oct 2008 16:25:27 +0200 Message-ID: <48EA1FD2.5080402@kkip.pl> Date: Mon, 06 Oct 2008 16:25:22 +0200 From: Bartosz Stec User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-User: admin@kkip.pl X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Spam-Score: -8.9 X-Spam-Score-Int: -88 X-Exim-Version: 4.69 (build at 26-Jun-2008 18:19:28) X-Date: 2008-10-06 16:25:27 X-Connected-IP: 192.168.0.10:3831 X-Message-Linecount: 42 X-Body-Linecount: 31 X-Message-Size: 1687 X-Body-Size: 1265 X-Received-Count: 1 X-Recipient-Count: 1 X-Local-Recipient-Count: 1 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 Subject: reloading samba config made system unresponsible X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Oct 2008 14:25:28 -0000 My tries to tune smb.conf to achieve better performance expose very strange bug: Just executing: /usr/local/etc/rc.d/samba reload made my system unresponsible from network. It happens three times until now so I'm sure that is the cause (but it happened after some succesful reloads a couple of minutes earlier, so it's not happening all the time command is executed). Symptoms: - machine only responding to ping requests - ssh session shows, that config reload was succesful, and that's last thing showed (no shell after message) - can't connect with another ssh session, but no refuse nor timeout - on local console system seems responsible (alt +[1-9] works), but any try to login cause it to wait forever for password prompt - no kernel or error message on screen, and nothing suspicious in logs - alt+ctrl+del does nothing - pressing power button and waiting for system to shutdown does nothing - hard reset was the only way - after first restart I've made full fsck and started rebuilding gmirror - when machine hangs second time rebuilding doesn't stop I'm not a developer but it looks like some kind of deadlock? Note that changes I made to smb.conf was only in socket options. -- Bartosz Stec