From owner-freebsd-questions@FreeBSD.ORG Mon Nov 13 15:46:23 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3913316A4AB for ; Mon, 13 Nov 2006 15:46:23 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail2.sea5.speakeasy.net (mail2.sea5.speakeasy.net [69.17.117.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAD8943DDB for ; Mon, 13 Nov 2006 15:42:58 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 14038 invoked from network); 13 Nov 2006 15:42:44 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail2.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 13 Nov 2006 15:42:44 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id B1E7228431; Mon, 13 Nov 2006 10:42:43 -0500 (EST) To: Garrett Cooper References: <4554EA97.1040908@u.washington.edu> From: Lowell Gilbert Date: Mon, 13 Nov 2006 10:42:43 -0500 In-Reply-To: <4554EA97.1040908@u.washington.edu> (Garrett Cooper's message of "Fri, 10 Nov 2006 13:09:43 -0800") Message-ID: <448xif5p58.fsf@be-well.ilk.org> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: (SAMBA) issue with filehandles being released under 6.1-RELEASE? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 15:46:23 -0000 Garrett Cooper writes: > Just wondering if anyone else was experiencing the same issues that I > am.. it's related to Samba-3.0.22c and sockets / filehandles. > > For some odd reason every couple days (~2 days) I have to restart the > smbd daemon because it eats up 6000+ filehandles, just for sockets I > assume (based on netstat output). At the point where it reaches 8000 > some filehandles open, the system refuses to fork, forcing me to login > as root on the console directly instead of via SSH. > > My machine is a local / preferred master (smbd fights with XP Home > clients because they want to be master browsers), with limited access > to a few XP clients (<4 clients at any given point in time), plus an > XBox using smbclient with XBox Media Center. > > Helpful info: > [root@hoover /home/gcooper]# uname -a > FreeBSD hoover.localdomain 6.1-RELEASE-p10 FreeBSD 6.1-RELEASE-p10 #9: > Mon Oct 16 02:14:29 PDT 2006 > gcooper@hoover.localdomain:/usr/obj/usr/src/sys/HOOVER i386 > > > /usr/local/etc/smb.conf: > [global] > workgroup = WORKGROUP > encrypt passwords = yes > log file = /var/log/samba/log.%m > log level = 3 passdb:4 auth:4 > # log level = 5 > socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 > local master = yes > preferred master = yes > dns proxy = no > guest ok = no > > [shared] > path = /shared > writeable = yes > public = yes > hosts deny = shiina pinocchio > guest ok = no > create mask = 0775 > > The only changes that I've made to smb.conf between now and when I > last accessed samba is that I've removed an unneeded share and removed > guest advertisement for my shares (need password / username anyhow to > login, so I figured I might as well..). This is a Samba issue, not an OS issue, as demonstrated by the fact that the system is able to close all of the handles when the daemon is shut down. Have you looked closely at the netstat output to which you referred? It would be interesting if all of the stuck connections were coming from the same host, or were in a particular state, etc.