From owner-freebsd-current@FreeBSD.ORG Sat Sep 25 20:07:51 2004 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 3CFDC16A4CE; Sat, 25 Sep 2004 20:07:51 +0000 (GMT) Received: from mail05.syd.optusnet.com.au (mail05.syd.optusnet.com.au [211.29.132.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E99F43D31; Sat, 25 Sep 2004 20:07:50 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) i8PK7mbT027868 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 26 Sep 2004 06:07:49 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])i8PK7lxP008861; Sun, 26 Sep 2004 06:07:47 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)i8PK7lrm008860; Sun, 26 Sep 2004 06:07:47 +1000 (EST) (envelope-from pjeremy) Date: Sun, 26 Sep 2004 06:07:47 +1000 From: Peter Jeremy To: Pawel Jakub Dawidek Message-ID: <20040925200747.GE83620@cirb503493.alcatel.com.au> References: <7m7jqjhojv.wl@black.imgsrc.co.jp> <20040924122508.GG9550@darkness.comp.waw.pl> <20040924143224.GG47816@dan.emsphone.com> <20040925095549.GH9550@darkness.comp.waw.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040925095549.GH9550@darkness.comp.waw.pl> User-Agent: Mutt/1.4.2i cc: Current Subject: Re: panic: swap_pager_isswapped: failed to locate all swap meta blocks 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: Sat, 25 Sep 2004 20:07:51 -0000 On Sat, 2004-Sep-25 11:55:49 +0200, Pawel Jakub Dawidek wrote: >On Fri, Sep 24, 2004 at 09:32:30AM -0500, Dan Nelson wrote: >+> Considering that the system is going down anyway, why bother? > >Because if you have swap on e.g. gmirror device, gmirror will rebuild >components on every boot, because components are marked dirty - >they were open for writing on shutdown, so it looks like a power failure. As an alternative approach, rather than marking swap clean on a shutdown, why not have a flag in the object's metadata that says "this object doesn't need synchronising on a reboot". If the flag is set, then gmirror just sets both sides as synchronised and active on boot. This is the approach taken by HP Tru64 LSM. (Though one improvement you could make over LSM would be to document the flag). -- Peter Jeremy