From owner-freebsd-hackers Fri Oct 27 18:55:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id ED0ED37B479; Fri, 27 Oct 2000 18:55:36 -0700 (PDT) Received: by relay.butya.kz (Postfix, from userid 1000) id 27A0628DA0; Sat, 28 Oct 2000 08:55:33 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 175EE28D7E; Sat, 28 Oct 2000 08:55:33 +0700 (ALMST) Date: Sat, 28 Oct 2000 08:55:33 +0700 (ALMST) From: Boris Popov To: Shawn Halpenny Cc: freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: smbfs-1.3.0 released In-Reply-To: <20001027111539.A391@nightrain.xelus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 27 Oct 2000, Shawn Halpenny wrote: > 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. I think that I've found possible cause of this problem and 1.3.1 will be released at this weekend. > Incidentally, under smbfs-1.2.7, the above scenario only caused 'ls' > to display 'broken pipe' and I could remount that share and things Yes, 'broken pipe' was a bug and now it should work properly. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message