Date: Fri, 20 Aug 2004 10:26:55 -0700 (PDT) From: Doug White <dwhite@gumbysoft.com> To: Martin Blapp <mb@imp.ch> Cc: freebsd-current@freebsd.org Subject: Re: SMP: Background fsck deadlocks CURRENT and RELENG_5 solid Message-ID: <20040820102415.T73388@carver.gumbysoft.com> In-Reply-To: <20040820081108.V95296@cvs.imp.ch> References: <20040819165405.D95296@cvs.imp.ch> <200408191107.31678.jhb@FreeBSD.org> <20040819190555.S66276@carver.gumbysoft.com> <20040820081108.V95296@cvs.imp.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 20 Aug 2004, Martin Blapp wrote: > > Perhaps you're short on disk space on / and the deltas from the snapshot > > take you over the edge? Or have some sort of large I/O operation run just > > after boot? > > Hmm of course yes. But only about 10 seconds on one machine. On the other > the workload just begins after startup. And, I start two kernel threaded > programms at the same time. > > If you like to have a similiar setup you have to install: > > clamd > mimedefang > sendmail (from ports) > dnsrbld > qpopper > apache > > I think that's enough and will lead to a crash. How big is the mail queue? There's some bugs in the snapshot code versus the background update, and touching a file that gets adjusted later will explode like this. Also just plain massive changes will do it -- a while back it was cvsupping ports while bgfsck was running. You migth want to set your spool volume nobgfsck. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040820102415.T73388>