From owner-freebsd-stable@FreeBSD.ORG Thu Dec 14 01:29:25 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 4EC2716A415 for ; Thu, 14 Dec 2006 01:29:25 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BBCE43D5A for ; Thu, 14 Dec 2006 01:27:21 +0000 (GMT) (envelope-from chrcoluk@gmail.com) Received: by nf-out-0910.google.com with SMTP id x37so649596nfc for ; Wed, 13 Dec 2006 17:28:49 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Ni/RbsgaBViPgXdXGMuu+yHSp1ECQ5sduScQpj+oMVsQGXZueVtXoBhRdUOa43upEiHCwe3A+O5/2SLiThK3yMDuLA9p85ahqeibFQPD37TWNwqYjATs2JiYoXiWmfYKbHU259C0r8NrFrjhrRVGE2nsUjg7+vTCMBhyxKJgOMw= Received: by 10.82.126.5 with SMTP id y5mr153739buc.1166059728895; Wed, 13 Dec 2006 17:28:48 -0800 (PST) Received: by 10.82.134.15 with HTTP; Wed, 13 Dec 2006 17:28:48 -0800 (PST) Message-ID: <3aaaa3a0612131728t214cf77djd0a9fd47f1b12021@mail.gmail.com> Date: Thu, 14 Dec 2006 01:28:48 +0000 From: Chris To: "Anish Mistry" In-Reply-To: <200612071349.54854.mistry.7@osu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20061123162813.L3026@volte.student.utwente.nl> <20061123192532.GA81937@xor.obsecurity.org> <3aaaa3a0612071036v2df98097ncf9c962e43e6f39d@mail.gmail.com> <200612071349.54854.mistry.7@osu.edu> 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, 14 Dec 2006 01:29:25 -0000 On 07/12/06, Anish Mistry wrote: > On Thursday 07 December 2006 13:36, 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 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' thread 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 the 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 > > > > 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. > > > > 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. > > > > So far I have not got my local bsd box up and running yet due to no > > keyboard still need parts for it. > I've updated the sshfs and libs port, you may want to update and see > if that helps. > > -- > Anish Mistry > > > Hi yes my sshfs and the libs got updated but didnt fix the crash however I did find this link. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1362611+0+archive/2006/freebsd-stable/20060702.freebsd-stable It does make sense if thats the problem since the entire server even locally stops working properly, and it always follows a unexpected nfs/sshfs disconnection ie. network timeout. I am now running 6.2-RC that has the new file and currently at 1 day 11hrs uptime. Chris