From owner-freebsd-current Mon Sep 21 04:12:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA18829 for freebsd-current-outgoing; Mon, 21 Sep 1998 04:12:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA18823 for ; Mon, 21 Sep 1998 04:12:17 -0700 (PDT) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id HAA09822; Mon, 21 Sep 1998 07:07:59 -0400 (EDT) Date: Mon, 21 Sep 1998 07:07:59 -0400 (EDT) From: Brian Feldman To: "Jordan K. Hubbard" cc: Terry Lambert , Peter Wemm , freebsd@timog.prestel.co.uk, current@FreeBSD.ORG Subject: Re: DEVFS & SLICE? In-Reply-To: <20714.906351954@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Funny thing is, for 23 days this computer survived a LOT of bashing on its MFS, and was stable. Here's a possibility: run a test system out of memory (and release it of course) including swap (you know swap_pager: out of memory), and see if it's still stable, as I think that may have been the problem. If so, maybe there aren't some memory allocation checks in the MFS code (I'll go through it today) which could have caused a kernel trap but still no panic? Cheers, Brian Feldman On Sun, 20 Sep 1998, Jordan K. Hubbard wrote: > > Hmm... reference to MFS working? Really? I seem to notice otherwise. For > > Probably seems that way due to insufficient gathering of evidence. > I've been using MFS on all my -current boxes for awhile and even set > the 32 minute "worldstone" record on the quad-Xeon box by sticking > /usr/src and /usr/obj entirely in the MFS (1GB of memory sure helps). > I experienced no crashes or instability that could be attributed to > MFS. > > - Jordan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message