From owner-freebsd-current Thu Apr 27 10: 7: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 43A9537BF5B for ; Thu, 27 Apr 2000 10:07:06 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA05542; Thu, 27 Apr 2000 10:06:57 -0700 (PDT) (envelope-from dillon) Date: Thu, 27 Apr 2000 10:06:57 -0700 (PDT) From: Matthew Dillon Message-Id: <200004271706.KAA05542@apollo.backplane.com> To: Brad Knowles Cc: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: Support for large mfs References: <200004270554.BAA34693@bb01f39.unx.sas.com> <200004270605.XAA00807@apollo.backplane.com> <200004271634.JAA05279@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : Do you have any thoughts on this subject? Is 3.2-RELEASE old and :non-optimized enough that it really could stand replacing? 3.2 is certainly old. The question is whether or not the performance issue that caught you under 3.2 is fixed under 4.0. Not knowing what was causing the hangups under 3.2 I can only guess that there's a 50-50 change it's been fixed in 4.0. I'm trying to think of what Diablo could be doing that would cause the system to stall on the history file, and I can't think of anything. It ought to work pretty well.... certainly as good or better then MFS, anyway. I suspect that if the issue still exists it's going to be something stupid simple that doing something trivial like turning off write-behind will fix. -Matt : Given some of the problems we've been seeing lately (which I'm :pretty sure are a result of running out of virtual memory and the :machine spontaneously rebooting), I think I might be able to convince :my management to spring for a third 2450, but with a slightly :different configuration than what I'll be using for the news reader :servers. : : It would help me formulate useful arguments for this proposal if :I had input from more knowledgeable people than I. : :-- : These are my opinions -- not to be taken as official Skynet policy :====================================================================== :Brad Knowles, || Belgacom Skynet SA/NV To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message