Date: Fri, 27 Oct 2000 11:15:39 -0400 From: Shawn Halpenny <malachai@iname.com> Cc: Boris Popov <bp@butya.kz>, freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: smbfs-1.3.0 released Message-ID: <20001027111539.A391@nightrain.xelus.com> In-Reply-To: <39F46B08.808132D2@owp.csus.edu> References: <Pine.BSF.4.10.10010200841510.13025-100000@lion.butya.kz> <39F46B08.808132D2@owp.csus.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001027111539.A391>