From owner-freebsd-current  Sun Jun 18 15:28:39 2000
Delivered-To: freebsd-current@freebsd.org
Received: from beastie.mckusick.com (beastie.mckusick.com [209.31.233.184])
	by hub.freebsd.org (Postfix) with ESMTP id 450E637BB37
	for <freebsd-current@freebsd.org>; Sun, 18 Jun 2000 15:28:32 -0700 (PDT)
	(envelope-from mckusick@mckusick.com)
Received: from beastie.mckusick.com (localhost [127.0.0.1])
	by beastie.mckusick.com (8.9.3/8.9.3) with ESMTP id PAA09503;
	Sun, 18 Jun 2000 15:28:23 -0700 (PDT)
	(envelope-from mckusick@beastie.mckusick.com)
Message-Id: <200006182228.PAA09503@beastie.mckusick.com>
To: Kevin Day <toasty@dragondata.com>
Subject: Re: Panic with userquota(softupdates?) 
Cc: freebsd-current@freebsd.org
In-Reply-To: Your message of "Fri, 16 Jun 2000 18:55:01 CDT."
             <200006162355.SAA03404@celery.dragondata.com> 
Date: Sun, 18 Jun 2000 15:28:23 -0700
From: Kirk McKusick <mckusick@mckusick.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

	From: Kevin Day <toasty@dragondata.com>
	Subject: Panic with userquota(softupdates?)
	To: freebsd-current@freebsd.org
	Date: Fri, 16 Jun 2000 18:55:01 -0500 (CDT)
	Cc: mckusick@mckusick.com

	I keep getting panics in dqget(ufs_quota.c), with a -current
	from a couple of days ago. I think this might be softupdates
	related, since I can't make it happen with softupdates
	turned off, although it's quite possible that it has nothing
	to do with it. Does anyone have any idea what might be
	causing this?

	Any other information that might be useful here?

	-- Kevin

I have just committed a change to sys/contrib/softupdates/ffs_softdep.c
(delta 1.68) which corrects a panic in the kernel when quotas and soft
updates are used together. While the specific problem that I fixed
appears somewhat different than the one you are reporting, it may be
related. I suggest that you update to the above delta and see if it
solves your problem. If your problem persists, let me know. As always,
if you can give a specific set of inputs which trigger the problem,
that is always helpful in tracking it down.

	Kirk McKusick


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message