From owner-freebsd-hackers Fri Oct 27 8:15:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zeus.lpa.com (mail.lpa.com [12.3.233.134]) by hub.freebsd.org (Postfix) with ESMTP id E2E7437B479; Fri, 27 Oct 2000 08:15:42 -0700 (PDT) Received: from xelus.com ([10.4.5.232]) by zeus.lpa.com (Netscape Messaging Server 4.15) with ESMTP id G33H1700.9FA; Fri, 27 Oct 2000 11:15:07 -0400 Date: Fri, 27 Oct 2000 11:15:39 -0400 From: Shawn Halpenny Cc: Boris Popov , freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: smbfs-1.3.0 released Message-ID: <20001027111539.A391@nightrain.xelus.com> References: <39F46B08.808132D2@owp.csus.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39F46B08.808132D2@owp.csus.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Speaking of smbfs, has anyone else run into an odd bug using it in 4.1.1-STABLE? Occasionally, if I run 'df' or try to access the directories (e.g. using 'ls') for an smbfs mount after a period of time during which there were no accesses across that mount point (e.g. mount, don't touch it for an hour, then try 'df'), my machine will reboot after a few seconds. No panic message or anything--it's just like I pressed the reset button. Incidentally, under smbfs-1.2.7, the above scenario only caused 'ls' to display 'broken pipe' and I could remount that share and things would be fine. 'df' would still work without any noticeable difference. Don't have any idea about starting to troubleshoot this one. -- Shawn Halpenny | Maniacal@I Ache, Ohm | "Universal Danger!" +- - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - \ | vi:G3kfM~lxfAPXh~l~2x2FirllpfcxlrifaprmfOX~Xp2hr.lrcelyl2p - - - - - - - -| fU~X~refsPprnlxppri2lxlpr,pFrpprrfaPlpfiprgllxp~3Xlpfndw To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message