From owner-freebsd-current Tue Oct 13 14:17:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26616 for freebsd-current-outgoing; Tue, 13 Oct 1998 14:17:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26611 for ; Tue, 13 Oct 1998 14:17:18 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.9.1) id XAA14689 for current@freebsd.org; Tue, 13 Oct 1998 23:17:02 +0200 (CEST) (envelope-from sos) Message-Id: <199810132117.XAA14689@sos.freebsd.dk> Subject: MFS broken on SMP ?? To: current@FreeBSD.ORG (FreeBSD current) Date: Tue, 13 Oct 1998 23:17:02 +0200 (CEST) From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just tried using an MFS /tmp filesystem, and that breaks under a new (~2 hours ago) current with SMP. It makes various things like make the compiler etc segfault pretty quickly on a make -j8 world. I think I've run with a MFS /tmp before under SMP, so it might be a recent breakage..... Ideas? observations? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message