From owner-freebsd-current@FreeBSD.ORG Sat Sep 25 17:11:25 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 BE0F716A4CE; Sat, 25 Sep 2004 17:11:25 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74A2343D1F; Sat, 25 Sep 2004 17:11:25 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.11/8.12.11) id i8PHBJnk065536; Sat, 25 Sep 2004 12:11:19 -0500 (CDT) (envelope-from dan) Date: Sat, 25 Sep 2004 12:11:19 -0500 From: Dan Nelson To: Pawel Jakub Dawidek Message-ID: <20040925171119.GA90839@dan.emsphone.com> 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> X-OS: FreeBSD 5.3-BETA5 X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: Jun Kuriyama 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 17:11:25 -0000 In the last episode (Sep 25), Pawel Jakub Dawidek said: > On Fri, Sep 24, 2004 at 09:32:30AM -0500, Dan Nelson wrote: > +> > This is indirectly caused by me. I added 'stop' method to > +> > rc.d/swap1 script and now swapoff(8) is done on every > +> > shutdown(8) run. > +> > > +> > Will it be possible to fix it or should I made this optional? > +> > +> 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. Can you clear the flag when all writes are synched (perhaps after a 2-sec delay)? Just because it's open for writing doesn't mean it's dirty. -- Dan Nelson dnelson@allantgroup.com