From owner-freebsd-current@FreeBSD.ORG Tue May 10 05:12:34 2005 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 9295B16A4EE for ; Tue, 10 May 2005 05:12:34 +0000 (GMT) Received: from lexi.siliconlandmark.com (lexi.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 280CC43D49 for ; Tue, 10 May 2005 05:12:34 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from lexi.siliconlandmark.com (localhost [127.0.0.1]) j4A5CUOQ025841 for ; Tue, 10 May 2005 01:12:30 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)j4A5CUiG025838 for ; Tue, 10 May 2005 01:12:30 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: lexi.siliconlandmark.com: andy owned process doing -bs Date: Tue, 10 May 2005 01:12:30 -0400 (EDT) From: Andre Guibert de Bruet To: current@freebsd.org Message-ID: <20050510001050.S750@lexi.siliconlandmark.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Information: Please contact the ISP for more information X-SL-MailScanner: Found to be clean X-SL-SpamCheck: not spam, SpamAssassin (score=-2.545, required 6, autolearn=not spam, AWL 0.05, BAYES_00 -2.60) X-MailScanner-From: andy@siliconlandmark.com Subject: VM pager subsystem shutdown? 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, 10 May 2005 05:12:34 -0000 Hi, Upon looking at the boot(9) code in kern_shutdown.c, it occured to me that there doesn't seem to be shutdown code for the VM pager subsystem. Is this done on purpose? If not, is creating a global-scope function in vm/swap_pager.c that iterates over the swdevt's in the LISTQ and feeds them swap_pager_swapoff() the simplest of ways of going about this? I stumbled upon this while analyzing the various vnodes still open at shutdown during the call to vfs_unmountall (See the patch in the "The "unmount of /dev failed (BUSY)" message, explained" thread). The only reason for the reference to /dev/amrd0s1b that I can think of would be the use of swap, and disabling it in fstab and re-performing the test confirms this. Please be gentle, I am still learning about our VM subsystem... :-) Andy /* Andre Guibert de Bruet * 6f43 6564 7020 656f 2e74 4220 7469 6a20 */ /* Code poet / Sysadmin * 636f 656b 2e79 5320 7379 6461 696d 2e6e */ /* GSM: +1 734 846 8758 * 5520 494e 2058 6c73 7565 6874 002e 0000 */ /* WWW: siliconlandmark.com * Tormenting bytes since 1980. */