Date: Wed, 21 Dec 1994 21:20:16 -0800 (PST) From: bmk@dtr.com To: fcawth@squid.umd.edu (Fred Cawthorne) Cc: questions@freebsd.org Subject: Re: Strange problems with quotas >1 disk. Message-ID: <199412220520.VAA09318@dtr.com> In-Reply-To: <9412222301.AA11911@squid.umd.edu> from "Fred Cawthorne" at Dec 22, 94 06:01:08 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > A few days ago I found the need to use quotas on another > > filesystem (/VOL2), which is on a different physical disk from > > /VOL2 (I doubt that matters). Since doing so, I have been plagued > > with intermittant page faults and reboots when I run any of the > > quota utilities. For example, quotacheck -v -a will often cause > > a reboot (no page fault) after it finishes checking /VOL1. edquota > > fails as well when it attempts to update user.quota, but it > > SOMETIMES gives a page fault (I didn't record the information, > > unfortunately). Usually it just reboots. Sometimes it even > > works like it should :). > > > ... > > Has anyone else seen this problem, or is it just me? > > > I have seen this on my system. (Just tried it...) > I have also seen one reboot when I was doing alot of quota changing on a > config with only one filesystem that had quotas. > (i.e. edquota a bunch of times...) It usually works correctly for > the single filesystem case, as you noted. When I enabled quotas on > a second filesystem, and ran quotacheck, it rebooted my machine!!!! > (I was running X, so I don't know if there was a message...) > Also, when it came back up, and tried to check the quotas, it said: > quotacheck: cannot allocate memory > (When quotacheck -a was run from the rc file) > I have 32 megs of ram, 64 megs of swap ... What gives???? I had forgotten about this symptom... Mine did this also. I have 32MB of ram and 128MB of swap. It's virtually impossible that I was out of memory unless quotacheck is leaking like a sieve. If I was to take a WAG about where the problem is, I'd start looking in the kernel quota routines... But then again, I'm not a kernel hacker. :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199412220520.VAA09318>