From owner-freebsd-stable@FreeBSD.ORG Thu Dec 10 02:10:12 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B37CE106568D for ; Thu, 10 Dec 2009 02:10:12 +0000 (UTC) (envelope-from mpp@mppsystems.com) Received: from mail929c35.nsolutionszone.com (mail929c35.nsolutionszone.com [209.235.152.119]) by mx1.freebsd.org (Postfix) with ESMTP id 626E28FC12 for ; Thu, 10 Dec 2009 02:10:12 +0000 (UTC) X-POP-User: mppsystems.gulftel.com Received: from mppsystems.com (99-194-190-48.dyn.centurytel.net [99.194.190.48]) by mail929c35.nsolutionszone.com (8.13.6/8.13.1) with ESMTP id nB9LqSS9010340 for ; Wed, 9 Dec 2009 21:52:29 GMT Received: by mppsystems.com (Postfix, from userid 1000) id 5A9DD17029; Wed, 9 Dec 2009 15:52:23 -0600 (CST) Date: Wed, 9 Dec 2009 15:52:23 -0600 From: Mike Pritchard To: Mikolaj Golub Message-ID: <20091209215223.GA1921@mppsystems.com> References: <86ws1180sr.fsf@kopusha.onet> <20091206181813.GR43143@deviant.kiev.zoral.com.ua> <86vdgjry3u.fsf@zhuzha.ua1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86vdgjry3u.fsf@zhuzha.ua1> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: Kostik Belousov , FreeBSD Stable Subject: Re: FreeBSD 7.1: QUOTA: kernel panics in jailed() X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Dec 2009 02:10:12 -0000 On Mon, Dec 07, 2009 at 10:23:49AM +0200, Mikolaj Golub wrote: > On Sun, 6 Dec 2009 20:18:13 +0200 Kostik Belousov wrote: > > > The kernel paniced because chkdq was supplied NULL credentials and > > _positive_ blocks use count change. Line 276 calls chkdq with > > -datablocks as the change. This could happen if you have problems > > either with hardware (e.g. memory or CPU cache), or your fs > > is damaged. > > > > Another possibility is random corruption of the kernel memory, but > > I recommend to start with fsck and then continue with memory testers > > if fsck have shown no problems. > > We have checked FS -- looks OK. So far we have just rebooted to the kernel > without quota. To check the hardware is in our plans. Thank you. Did you happen to turn quotas off then back on for the file system in question? -- Mike Pritchard mpp @ FreeBSD.org "If tyranny and oppression come to this land, it will be in the guise of fighting a foreign enemy." - James Madison (1787)