Date: Wed, 12 Mar 2003 10:33:02 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Jake Burkholder <jake@locore.ca> Cc: Hiroki Sato <hrs@eos.ocn.ne.jp>, freebsd-sparc@FreeBSD.ORG Subject: Re: NFS problem? Message-ID: <20030312183302.GB86590@rot13.obsecurity.org> In-Reply-To: <20030312113545.A50948@locore.ca> References: <20030312.212909.71544461.hrs@eos.ocn.ne.jp> <20030312113545.A50948@locore.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
--i9LlY+UWpKt15+FH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Mar 12, 2003 at 11:35:45AM -0500, Jake Burkholder wrote: > Kris Kennaway has reported a similar problem, but iirc it was the > opposite; with 4.x the server would crash and upgrading it to 5.0 > fixed it. I have no idea what could cause it though. I use nfs > pretty heavily between my sparc64 development machines and a 4.x > x86 server and have never seen this. I suspect what I was doing to the thing counts as even heavier, though :) Package builds do a *lot* of concurrent accesses to the NFS volume including copying around large files. I saw this (=double fault) on two package build master machines until I upgraded them to 5.0. I've not seen a problem with the 5.0 i386 server under the same conditions. Kris --i9LlY+UWpKt15+FH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+b31eWry0BWjoQKURAq1nAJ0RfX7iqfqa6wo1NSHOWUq8budV0wCgsZRr ssKWOLjJEPeWeu8RkXqI/ac= =FhJg -----END PGP SIGNATURE----- --i9LlY+UWpKt15+FH-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-sparc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030312183302.GB86590>