Date: 22 Aug 2001 01:37:52 +0200 From: Dag-Erling Smorgrav <des@ofug.org> To: Matt Dillon <dillon@earth.backplane.com> Cc: Alfred Perlstein <bright@mu.org>, John Baldwin <jhb@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_condvar.c kern_synch.c src/sys/sys proc.h Message-ID: <xzppu9p7zn3.fsf@flood.ping.uio.no> In-Reply-To: <200108212254.f7LMsFQ68740@earth.backplane.com> References: <200108211842.f7LIgkp03186@freefall.freebsd.org> <20010821134601.J81307@elvis.mu.org> <xzppu9p1b29.fsf@flood.ping.uio.no> <xzpy9od11uv.fsf@flood.ping.uio.no> <xzpu1z111mi.fsf@flood.ping.uio.no> <200108212254.f7LMsFQ68740@earth.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Matt Dillon <dillon@earth.backplane.com> writes: > :8% averaged over the machine's uptime, in fact: > : > :root@des /sys/kern# uptime > :12:31AM up 5 days, 10:27, 7 users, load averages: 1.94, 1.57, 1.69 > :root@des /sys/kern# ps -axlp 5 > : UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND > : 0 5 0 142 20 0 0 0 syncer DL ?? 629:49.14 (syncer) > [...] > The syncer is not typically fragile. The only thing I can think of > that could cause something like this to happen is if 'rushjob' > (aka speedup_syncer()) is being called continuously. After some discussion with jhb on IRC, I rebooted in single-user mode and ran 'fsck -y' on all file systems. It found several unreferenced directories and files on / and /home, and a handful of incorrect link counts. Background fsck is now off, and I'm somewhat confident my interrupt latency problems will not resurface, though it's too early to tell. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzppu9p7zn3.fsf>