From owner-freebsd-questions Mon Feb 26 17:56:04 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA07811 for questions-outgoing; Mon, 26 Feb 1996 17:56:04 -0800 (PST) Received: from mpp.minn.net (root@mpp.Minn.Net [204.157.201.242]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA07735 for ; Mon, 26 Feb 1996 17:55:59 -0800 (PST) Received: (from mpp@localhost) by mpp.minn.net (8.7.3/8.6.9) id SAA13737; Mon, 26 Feb 1996 18:40:15 -0600 (CST) Message-Id: <199602270040.SAA13737@mpp.minn.net> Subject: Re: quotacheck runs away and crashes system.. argh! To: swaits@pr.erau.edu (Stephen Waits) Date: Mon, 26 Feb 1996 18:40:15 -0600 (CST) From: "Mike Pritchard" Cc: questions@FreeBSD.ORG In-Reply-To: from "Stephen Waits" at Feb 26, 96 01:23:54 pm X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.ORG Precedence: bulk Stephen Waits wrote: > > > I decided today I'd get quota's working on our system. > > I did the following: > > touch /usr/quota.users > chown root.wheel /usr/quota.users > chmod 600 /usr/quota.users You don't need to create a zero length quota file first. Enabling quotas in fstab and sysconfig and then rebooting will establish the new quota file for you. > Edited /etc/fstab: > > /dev/sd0s1f /usr ufs rw,userquota 1 1 > > Edited /etc/sysconfig: > > check_quotas=YES > > REBOOTED.. The system booted fine until it said it was checking the > quotas. The drive chugged along for awhile, then. .. silence.. > > > SO, I changed /etc/sysconfig back to check_quotas=NO, rebooted, and ran > quotacheck -av manually with top running on another VTY. > > quotacheck chugged through the disk for a bit, then spit out a bunch of > "fixed:" lines showing the updates it was making, then sat there. Now, a > look at top showed it starting to run like crazy as soon as the "sitting > there" begins. Any ideas? tia. I suspect that you have some very large uids in your file system. Quotacheck is not very efficient and if you have some very large uids, or very large gaps between uids, quotacheck can run for a very long time. You might want to pick up the quotacheck from -current and run it with the "-v" option to see if it complains about unknown uids. You could also run find with the -nouser option. The "fixed:" lines were probably the result of running quotacheck on an active filesystem and the fact that you had interrupted quotacheck earlier. -- Mike Pritchard mpp@minn.net "Go that way. Really fast. If something gets in your way, turn"