From owner-freebsd-current@FreeBSD.ORG Sun Oct 17 04:37:10 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 E8BFA16A4CF; Sun, 17 Oct 2004 04:37:10 +0000 (GMT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5A3543D41; Sun, 17 Oct 2004 04:37:09 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.1/8.13.1) with ESMTP id i9H4axB4085154; Sat, 16 Oct 2004 21:37:03 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200410170437.i9H4axB4085154@gw.catspoiler.org> Date: Sat, 16 Oct 2004 21:36:58 -0700 (PDT) From: Don Lewis To: pjd@FreeBSD.org In-Reply-To: <20041016062115.GS73767@darkness.comp.waw.pl> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: ache@nagual.pp.ru cc: scottl@FreeBSD.org cc: current@FreeBSD.org Subject: Re: Stable panic on shutdown: swapoff: failed to locate N swap 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: Sun, 17 Oct 2004 04:37:11 -0000 On 16 Oct, Pawel Jakub Dawidek wrote: > On Sat, Oct 16, 2004 at 08:54:47AM +0400, Andrey Chernov wrote: > +> On Sat, Oct 16, 2004 at 12:47:31AM -0400, David Schultz wrote: > +> > Pawel has a patch that moves the swapoff() later in the shutdown > +> > sequence, after all user processes have been killed. It should > +> > make swapoff() basically a no-op / sanity check, since nothing > +> > should actually be paged out at that point. > +> > +> Forward it to me, please, I'll test it. > > http://people.freebsd.org/~pjd/patches/swapoff_all.patch > This should probably be combined with vfs_umountall() to handle the mutual interdependencies between regular file systems, file systems stored on swap-backed md devices, and vnode-backed md devices used for swap. I have no idea how difficult this might be to implement. Hopefully nobody swaps to a vnode-backed md device that resides in a file system that is stored on a swap-backed md device ...