Date: Fri, 04 Jan 2002 08:10:53 -0500 From: Mike Tancsa <mike@sentex.net> To: freebsd-stable@FreeBSD.ORG Subject: quota.user (was Re: Strange problem with 3 kernel options Message-ID: <5.1.0.14.0.20020104080937.04e72370@marble.sentex.ca> In-Reply-To: <5.1.0.14.0.20020103093101.01be8a50@marble.sentex.ca> References: <3C3468D3.3785E6F7@garbonzo.hos.ufl.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
OK, on the machine in question, killing the quota.user files and letting
them be regenerated fixed the problem. I still have the bogus ones that
were causing the machine to hang in case someone is interested.
---Mike
At 09:32 AM 1/3/02 -0500, Mike Tancsa wrote:
>Thanks, they were all upgraded. I still suspect the corrupted quota.user
>file. I am going to try and find time this weekend to simulate it by
>manually corrupting the file and see if that causes the same behaviour on
>a test machine.
>
> ---Mike
>
>At 09:21 AM 1/3/02 -0500, Bob Johnson wrote:
>
>>Did you upgrade world when you upgraded the kernel? It sounds like
>>they are out of sync.
>>
>>
>>- Bob
>>
>> >
>> > Date: Wed, 02 Jan 2002 11:25:06 -0500
>> > From: Mike Tancsa <mike@sentex.net>
>> > Subject: Re: Strange problem with 3 kernel options
>> >
>> > OK, a quick update. I tried building another machine with the same
>> hardware
>> > (minus the realtek) and it works just fine. Its not nearly as busy as the
>> > one that failed. However, I did notice that the quota.users files on the
>> > two partitions had strange time stamps of the last access. Is it possible
>> > that the OS was unable to write to these corrupted files, and this is
>> where
>> > everything was holding up ? Anyways, I blew away those files and will try
>> > a reboot in the early hours to see if that makes a difference-- i.e.
>> with a
>> > freshly created quota.user file.
>> >
>> > ---Mike
>> >
>> > At 08:45 AM 1/2/02 -0500, Mike Tancsa wrote:
>> >
>> > >OK, I know I will get slapped for providing such little information (to
>> > >start), but this morning I had a bit of fun with upgrading a Oct19 kernel
>> > >to a Dec31st kernel. Getting rid of
>> > >
>> > >#options DUMMYNET
>> > >#options IPDIVERT #divert sockets
>> > ># Disk quotas are supported when this option is enabled.
>> > >#options QUOTA #enable disk quotas
>> > >
>> > >allowed me to have the machine function in a normal state. The problem
>> > >state was that I was unable to login to the system in multi user mode.
>> > >There *seemed* to be a lot of processes blocking on something. I dont
>> > >know what as I was unable to login. I thought at first it was that
>> syslog
>> > >problem with /dev/console, but I rebooted with syslogd off and I was able
>> > >to get to a login prompt briefly. After that the system became unstable
>> > >with too many files open I had to reboot.
>> > >
>> > >I am posting this in case anyone else has seen something similar.
>> > >
>> > >dmesg below. Kernel config is basically GENERIC with uneeded device
>> > >drivers removed. MAXUSERS is set at 256.
>> > >
>> > >As the box is production, I cant fiddle with it right now, but I can come
>> > >back in during off hours and do whatever would be useful to try and track
>> > >this down. I do have another box with quotas enabled, but its nowhere
>> > >nearly as busy, particularly as I tried to bring up quota support on my
>> > >mail partition which is fairly busy. (mount with soft updates
>> > >enabled). Anyone see anything similar ?
>> >
>
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-stable" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.1.0.14.0.20020104080937.04e72370>