From owner-freebsd-bugs  Sat Mar 14 14:50:04 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA13425
          for freebsd-bugs-outgoing; Sat, 14 Mar 1998 14:50:04 -0800 (PST)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA13386;
          Sat, 14 Mar 1998 14:50:02 -0800 (PST)
          (envelope-from gnats)
Date: Sat, 14 Mar 1998 14:50:02 -0800 (PST)
Message-Id: <199803142250.OAA13386@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: gene@cif.rochester.edu
Subject: Re:bin/4975:quotaonwhileserververybusycauseslockup/reboot
Reply-To: gene@cif.rochester.edu
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR bin/4975; it has been noted by GNATS.

From: gene@cif.rochester.edu
To: freebsd-gnats-submit@freebsd.org, toasty@dragondata.com
Cc:  Subject: Re:bin/4975:quotaonwhileserververybusycauseslockup/reboot
Date: Sat, 14 Mar 1998 17:44:05 -0500 (EST)

 I would like to bring this pr once again to the attention of the freebsd-bugs
 readers.  I have been able to produce this behaviour under low load at
 seemingly random times under FreeBSD 2.2.5-RELEASE.  Twice within about six
 hours quotaon -a hung the system.  I believe this pr should be upgraded
 to a priority of medium or critical as I am currently running a prduction
 system with quotas off because I cannot afford the crashes.
 
 However, I do have good news in this gloom and doom.  That is that I was
 able to get kernel backtraces of the system each time it was in a crash state.
 Both times, the kernel packed "page fault in kernel address space" (or similar)
 in the dqget() function.  That may be of some help in finding the problem.
 I'm thinking it is a dma concurrency issue possibly or a race condition that
 may have its real origins in the vfs, but I'm neither an i386 junky nor
 a person familiar with the new FreeBSD vfs, so I can't go bug-hunting.
 
 If someone eneds some other informaiton on this, please feel free to contact
 me.
 
 Gene
 

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