From owner-freebsd-current Sat Oct 17 04:58:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA05449 for freebsd-current-outgoing; Sat, 17 Oct 1998 04:58:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA05441; Sat, 17 Oct 1998 04:58:53 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id HAA09549; Sat, 17 Oct 1998 07:56:59 -0400 (EDT) Date: Sat, 17 Oct 1998 07:56:58 -0400 (EDT) From: Chuck Robey To: =?iso-8859-1?Q?S=F8ren_Schmidt?= cc: donegan@quick.net, freebsd-current@FreeBSD.ORG Subject: Re: softupdates/smp In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 17 Oct 1998, Chuck Robey wrote: > On Sat, 17 Oct 1998, Søren Schmidt wrote: > > > In reply to Chuck Robey who wrote: > > > On Fri, 16 Oct 1998, Steven P. Donegan wrote: > > > > > > > After a long biz trip and other adventures... > > > > > > > > I finally got back to the list, and compiled today's kernel (SMP). Tried > > > > a boot - no problem. Turned on softupdates on the disk (tunefs -n > > > > enable). Boot proceeded and then tombstone. Is softupdates viable on > > > > anyone's hardware at present under SMP? > > > > > > Solid here. With CAM and softupdates. Buildworlds like crazy. Wasn't > > > always that way, but is now. Real good, this machine get's used heavily > > > for schoolwork (I shouldn't run current on it, but I've been too heavily > > > infected with FreeBSD). > > > > > > It's a dual P6-166, Tyan Titan II. Wouldn't part with it for the world. > > > > You are lucky I guess, I still think we have race problems in there, at > > least it breaks real fast on a make work -j8 or above on resonably > > fast hardware here, and remember your filesystem is then beyond repair... > > I don't doubt that. I know longer think it's just a smp only breakage, > tho, something is complicating it. I've had those dumps, but luckily > the filesystems I do that with, I could regenerate. Not my cvs. I better amend that. I used to have the problems you have now, but they went away at least a month ago. Can't say why, exactly. Went off softupdates for a while, did a large number of extra fsck checks, went back on softupdates (after CAM came live) and now, well, it just works. Fine. Keeping one rabbit's foot quite handy. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message