From owner-freebsd-current@FreeBSD.ORG Mon Sep 1 17:04:29 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F24516A4BF for ; Mon, 1 Sep 2003 17:04:29 -0700 (PDT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B75F43F93 for ; Mon, 1 Sep 2003 17:04:28 -0700 (PDT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 5878672DA2; Mon, 1 Sep 2003 17:04:28 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 53B5F72DA0 for ; Mon, 1 Sep 2003 17:04:28 -0700 (PDT) Date: Mon, 1 Sep 2003 17:04:28 -0700 (PDT) From: Doug White To: freebsd-current@freebsd.org Message-ID: <20030901165035.D58395@carver.gumbysoft.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: swapon vs savecore dilemma X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Sep 2003 00:04:29 -0000 Hey folks, It looks like we may need to rethink the way swap is mounted at boot time if we want crashdumps to work. Recently(?), a change was made so you can no longer open a swap partition read/write after it is activated with swapon(8). In the current boot sequence, swap is mounted before the root fsck starts so additional space is available if the root fsck needs it. But at that point no partitions are available for writing a core to, so we can't run savecore then. Without crashdumps debugging gets kind of interesting. Suggestions, other than have separate dump and swap partitions? -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org