From owner-freebsd-current  Sat May 23 22:11:45 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA10401
          for freebsd-current-outgoing; Sat, 23 May 1998 22:11:45 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10390
          for <freebsd-current@FreeBSD.ORG>; Sat, 23 May 1998 22:11:34 -0700 (PDT)
          (envelope-from michaelh@cet.co.jp)
Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id FAA03382; Sun, 24 May 1998 05:10:28 GMT
Date: Sun, 24 May 1998 14:10:28 +0900 (JST)
From: Michael Hancock <michaelh@cet.co.jp>
To: Terry Lambert <tlambert@primenet.com>
cc: scrappy@hub.org, freebsd-current@FreeBSD.ORG
Subject: Re: May 17th UP machine 'panic'
In-Reply-To: <199805231956.MAA10465@usr07.primenet.com>
Message-ID: <Pine.SV4.3.95.980524140422.3345B-100000@parkplace.cet.co.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, 23 May 1998, Terry Lambert wrote:

> > I'll take a look at this.  Are you using quotas?
> 
> I am, I don't know if he is.
> 
> The problem is in the vput in quotaoff for the group quota file
> when doing a quotaoff on the user quota file.
> 
> Basically, the locking semantics of vget/vput pairings have apparently
> become assymetric?

vget() is confusing, because the lock flag means don't lock when 0, but
lock if LK_{lock flags} are passed.  vput() will always unlock.  But I
don't think this is the problem.

> In any case, there is a traversal of the vp's on a mount point
> in order to accredit all quota information correctly, and it is
> during this traversal that the failur occurs.
> 
> This is fairly easy to reproduce; enable user and group quotas,
> have the quota files in the / of the FS being quota'ed, and
> then do a shutdown.  The panic occurs during shutdown.

The problem seems to be a lock ownership problem rather than a missing
unlock.

Regards,


Mike Hancock


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