From owner-freebsd-stable@FreeBSD.ORG Thu Dec 7 18:48:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3E3DB16A40F for ; Thu, 7 Dec 2006 18:48:31 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE87843D8A for ; Thu, 7 Dec 2006 18:43:28 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id B33451A3C20; Thu, 7 Dec 2006 10:44:13 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 1B344513BC; Thu, 7 Dec 2006 13:44:09 -0500 (EST) Date: Thu, 7 Dec 2006 13:44:08 -0500 From: Kris Kennaway To: Chris Message-ID: <20061207184408.GA31535@xor.obsecurity.org> References: <20061123162813.L3026@volte.student.utwente.nl> <20061123192532.GA81937@xor.obsecurity.org> <3aaaa3a0612071036v2df98097ncf9c962e43e6f39d@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="J/dobhs11T7y2rNN" Content-Disposition: inline In-Reply-To: <3aaaa3a0612071036v2df98097ncf9c962e43e6f39d@mail.gmail.com> User-Agent: Mutt/1.4.2.2i Cc: s.c.sprong@student.utwente.nl, freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: sshfs/nfs cause server lockup 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: Thu, 07 Dec 2006 18:48:31 -0000 --J/dobhs11T7y2rNN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 07, 2006 at 06:36:10PM +0000, Chris wrote: > On 23/11/06, Kris Kennaway wrote: > >On Thu, Nov 23, 2006 at 04:38:48PM +0100, s.c.sprong@student.utwente.nl= =20 > >wrote: > >> Chris wrote: > >> >kris a development on this, someone else posted about a nfs problem > >> >and reading his post some starkling point he made about network cards, > >> >he stated he only gets the bug on sis rl and fxp. > >> > >> Sorry for the misunderstanding, but I think that the 'NFS via TCP' thr= ead > >> covers other bugs, ie the inability to mount NFS v3 over TCP. > >> > >> I've tested the cards above, and the person I replied to encountered t= he > >> same bug with a bge card. My solution was to remove custom nfs settings > >> in sysctl.conf. I don't know which one was the culprit because I don't > >> have the time to look into it further. > >> > >> My poking uncovered a set of crashing bugs and potentially a livelock. > >> I would agree that NFS is very fragile in RELENG_6. > >> So far I've not run into an NFS server deadlock you > >> described. > > > >Are you sure these are NFS problems and not ethernet driver problems? > > > >Kris > > > > > > >=20 > Had another lockup today, reattached to screen process to see both > sshfs mounts timed out when running sshfs to remount the terminal > stopped updating, it didnt disconnect me and an ircd running on the > server remained functional and the server responded to pings, however > the terminal was dead and I couldnt login on ssh for a new session, a > ctrl-alt-del also failed to reboot it and it needed a power cycle > again. >=20 > I have googled researched and read dozens and dozens of nfs bug > reports where most of them seem to be a problem caused by nfs not > disconnecting properly leaving itself in a bad state, the fix is > usually to reboot. I am having to reboot weekly more often then my > windows desktop pc, everyone else having no problems with the nfs on > their linux servers having no problems and its hardly inspiring that > the stable freebsd is not stable. All these problems on google didnt > get fixed no dev attention etc. They probably got "no dev attention" because the user didn't submit any usable information ;-) Yes, that's a hint. If this problem really is important to you then you need to find the time to set up a suitable debugging environment so the developers can begin to help you. Until then we can't do anything no matter how many emails you send. > So far I have not got my local bsd box up and running yet due to no > keyboard still need parts for it. Kris --J/dobhs11T7y2rNN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFeGD0Wry0BWjoQKURAirDAKDKxW0OgWui0Ni22AqufYmqvpHRaACfU25H 3M2i4z2ltYZADGlQgC/tWvM= =UyFh -----END PGP SIGNATURE----- --J/dobhs11T7y2rNN--