Date: Sat, 14 Mar 1998 23:24:29 -0500 From: Gene Skonicki <gene@cif.rochester.edu> To: "Matthew N. Dodd" <winter@jurai.net> Cc: gene@cif.rochester.edu, freebsd-bugs@hub.freebsd.org Subject: Re: bin/4975:quotaonwhileserververybusycauseslockup/reboot Message-ID: <199803150424.XAA16383@roundtable.cif.rochester.edu> In-Reply-To: Your message of "Sat, 14 Mar 1998 23:05:43 EST." <Pine.BSF.3.96.980314230300.1171J-100000@sasami.jurai.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Let em clarify. I normally activate quotas at bootup (I was messing with
things a bit when I produced the error the first time). However, I have also
seen panic tracebacks that come through ffs_write() whihc indicates to me
some unpleasant implications. Otherwise, I wouldn't have a problem simply
turning quotas on. I really would liek to reproduce this, but I can't very
wel afford to on this machine---too many simultaneous and demands on it, etc.
Gene
On Sat, 14 Mar 1998 23:05:43 -0500 (EST), "Matthew N. Dodd" wrote:
>On Sat, 14 Mar 1998 gene@cif.rochester.edu wrote:
>> 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 think that you are probably the only one that is encountering this bug
>because everyone else is turning quotas on at boot, when the system is
>more or less idle.
>
>I've been running quotas on my system since 2.1R with no problems.
>
>You should not be doing quota{on,off,check} on active filesystems.
>
>/*
> Matthew N. Dodd | A memory retaining a love you had for life
>
> winter@jurai.net | As cruel as it seems nothing ever seems to
> http://www.jurai.net/~winter | go right - FLA M 3.1:53
>*/
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803150424.XAA16383>