From owner-freebsd-current@FreeBSD.ORG Sat Oct 16 02:41:00 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 26B6B16A4CE; Sat, 16 Oct 2004 02:41:00 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83AA843D45; Sat, 16 Oct 2004 02:40:59 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.200] ([192.168.254.200]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i9G2euLR027616; Fri, 15 Oct 2004 20:40:57 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <417089E6.8030105@freebsd.org> Date: Fri, 15 Oct 2004 20:39:34 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Schultz References: <20041015075641.GA6820@nagual.pp.ru> <20041015171144.GA69709@VARK.MIT.EDU> <20041015171700.GA74901@nagual.pp.ru> <20041016021131.GA72979@VARK.MIT.EDU> In-Reply-To: <20041016021131.GA72979@VARK.MIT.EDU> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: Andrey Chernov 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: Sat, 16 Oct 2004 02:41:00 -0000 David Schultz wrote: > On Fri, Oct 15, 2004, Andrey Chernov wrote: > >>On Fri, Oct 15, 2004 at 01:11:45PM -0400, David Schultz wrote: >> >>>On Fri, Oct 15, 2004, Andrey Chernov wrote: >>> >>>>N of blocks can be different. >>>>Can't provide full debugging trace yet, excepting this one: >>> >>>The traceback won't be very helpful in this case because this most >>>likely indicates a swap leak that happened some time earlier. >>>What *would* be helpful is more information about your swap >>>devices, any steps you need to take while the system is running to >>>reproduce this, the approximate size of N, etc. >> >># swapinfo >>Device 1K-blocks Used Avail Capacity >>/dev/da0s1b 615408 41408 574000 7% >> >>Nothing special to reproduce, it is always reproduced automatically at >>shutdown. > > > You're clearly using some of that swap space for something, so it > would be great if you could narrow it down a bit more. For > instance, does the problem only occur if you shut the system down > after having run particular applications? Are there ever any disk > errors? > > I'll poke around and see if I can find anything by inspection. > phk's rotitilling of the swap subsystem introduced a number of new > nits, but no serious bugs that I can see... > > >>Kernels from Aug 8 and below never do that, I see this panic constantly >>only with most recent kernels (last 2 days). I not test kernels between >>Aug 8 and last 2 days, so can't say anything. > > > The bug was probably introduced earlier, either by me, Alan, or > phk, but the swapoff codepath wasn't routinely exercised until > recently. FWIW, I think that doing a swapoff in the shutdown path is just asking for trouble. Fixing whatever bug this is would of course be nice, but the need for swapoff here is a hack and only opens up up to problems. Scott