From owner-freebsd-current Tue Jan 11 23: 9:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 96DF714D77 for ; Tue, 11 Jan 2000 23:09:33 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id XAA05255; Tue, 11 Jan 2000 23:32:50 -0800 (PST) Date: Tue, 11 Jan 2000 23:32:50 -0800 From: Alfred Perlstein To: Matthew Dillon Cc: "Russell L. Carter" , "Dave J. Boers" , freebsd-current@FreeBSD.ORG Subject: Re: Still system hangs, but different Message-ID: <20000111233250.R9397@fw.wintelcom.net> References: <20000112054825.436AB61@pinyon.org> <200001120703.XAA67832@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001120703.XAA67832@apollo.backplane.com>; from dillon@apollo.backplane.com on Tue, Jan 11, 2000 at 11:03:27PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matthew Dillon [000111 23:27] wrote: > :%:I have. > :% > :% Wait a sec. I've reviewed all the messages from you and I think something > :% got mixed together. I'm not convinced that your particular problems > :% are softupdates related. I recommend turning off softupdates entirely > :% for a few days to find out. > : > :Oh they are quite surely softupdates related. > : > :I got the "X still sorta works but anything that touches the disk wedges" > :flu today on a very current current. Triggered by a cc build on > :(soft) linked filesystem, cured by reverting back a week or so. > : > :And yes, it is quite certainly v. 1.47 and ata. > : > :NBD..., if it was a real barrier to progress I'd disable softupdates. > : > :Regards, > :Russell > > I think what we need to concentrate on is figuring out exactly what > is being wedged on. Hence my DDB suggestion below. > > Reverting to an old -current doesn't guarentee that it's softupdates. > If you turn off softupdates with tunefs on the filesystems and see > if it occurs with a new kernel that will tell us for sure. (But the > DDB suggestion is more important, that will tell us exactly what is > going on). I'm finding it easy to reboot a box by simply doing a cvsup and downloading a repo, I'm recompiling everything right now without softupdates but if you wanted what seems to be an easy to reproduce crash, try checking out the postgresql repo via cvsup. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message