Date: Sun, 26 Nov 2006 13:18:03 +0000 From: Chris <chrcoluk@gmail.com> To: "Kris Kennaway" <kris@obsecurity.org> Cc: s.c.sprong@student.utwente.nl, freebsd-stable@freebsd.org Subject: Re: sshfs/nfs cause server lockup Message-ID: <3aaaa3a0611260518x47ce56acqa45888fbd315e3fd@mail.gmail.com> In-Reply-To: <20061123192532.GA81937@xor.obsecurity.org> References: <20061123162813.L3026@volte.student.utwente.nl> <20061123192532.GA81937@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23/11/06, Kris Kennaway <kris@obsecurity.org> wrote: > On Thu, Nov 23, 2006 at 04:38:48PM +0100, s.c.sprong@student.utwente.nl wrote: > > Chris <chrcoluk@gmail.com> 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 <fingers crossed> I've not run into an NFS server deadlock you > > described. > > Are you sure these are NFS problems and not ethernet driver problems? > > Kris > > > The consistency is the servers that lock up are fine when not using any nfs or sshfs mounts. But the 2 servers that are fine use dc and re network adaptors. I am not able to setup my local bsd box until a new hd arrives next monday and will be a day or so before I get it setup to mirror the production conditions of the servers and I will then mount some nfs on it to repeat the problem. Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3aaaa3a0611260518x47ce56acqa45888fbd315e3fd>