Date: Mon, 10 Jul 2006 01:39:01 -0400 (EDT) From: Charles Sprickman <spork@bway.net> To: Kostik Belousov <kostikbel@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: 6.1 quota issues Message-ID: <Pine.OSX.4.61.0607100137200.3261@white.nat.fasttrackmonkey.com> In-Reply-To: <20060710052513.GF37822@deviant.kiev.zoral.com.ua> References: <Pine.OSX.4.61.0607072227510.3261@white.nat.fasttrackmonkey.com> <20060708085132.GD98476@over-yonder.net> <Pine.OSX.4.61.0607100039100.3261@white.nat.fasttrackmonkey.com> <20060710052513.GF37822@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 10 Jul 2006, Kostik Belousov wrote: > On Mon, Jul 10, 2006 at 12:41:07AM -0400, Charles Sprickman wrote: >> On Sat, 8 Jul 2006, Matthew D. Fuller wrote: >> >>> On Fri, Jul 07, 2006 at 10:56:47PM -0400 I heard the voice of >>> Charles Sprickman, and lo! it spake thus: >>>> >>>> Trying again, it reported the same inconsistencies then sat there >>>> for more than an hour taking up all the available CPU on the box >>>> until I killed it. The mtime on quota.user had not changed during >>>> the run. >>> >>> FWIW, I saw this on a box I setup running a late November -CURRENT >>> last year; I could never get the quotas setup and running right >>> because the check always just looped itself up. The partition they're >>> on has about 3 gig used out of ~45, with maybe a dozen users. I never >>> spent much time on it, since it's just a personal box, and the quotas >>> are mostly just to provide a handy measure of who's using what (no >>> limits set). I just gave it up and decided to worry about it later. >> >> What should I do here? It's consistently failing. What information >> should I gather to forumulate a PR that won't burden the assignee with >> lots of troubleshooting mess? The machine is not in production, but there >> is user data on it. I could allow a trusted developer access to it, or >> even create another jail to illustrate the problem. > > It is not clear from your report whether you run fsck on the problem > partition. I think (and my view is backed by "unexpected inconsistencies" > message) that this is the must. Sorry about that, I did not mention it, but thinking the same thing you did, I unmounted the partition and fsck'd twice for good measure. Both runs came back clean. I think its quotacheck complaining about the quota.user file... Thanks, Charles
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.OSX.4.61.0607100137200.3261>