From owner-freebsd-current Thu Sep 17 10:12:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14681 for freebsd-current-outgoing; Thu, 17 Sep 1998 10:12:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14674 for ; Thu, 17 Sep 1998 10:12:16 -0700 (PDT) (envelope-from thomma@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h016b.s86b1.BayNetworks.COM [134.177.1.107] (may be forged)) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id KAA01534; Thu, 17 Sep 1998 10:11:54 -0700 (PDT) Received: from fedex.engwest.baynetworks.com (fedex.engwest.baynetworks.com [134.177.110.46]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with SMTP id KAA01711; Thu, 17 Sep 1998 10:11:53 -0700 (PDT) Received: from carrera.engwest (carrera.engwest.baynetworks.com) by fedex.engwest.baynetworks.com (4.1/SMI-4.1) Received: from localhost by carrera.engwest (SMI-8.6/SMI-SVR4) id KAA08878; Thu, 17 Sep 1998 10:08:45 -0700 To: ben@rosengart.com, benedict@echonyc.com Cc: current@FreeBSD.ORG Subject: Re: soft updates panic once more; downgrading In-Reply-To: Your message of "Thu, 17 Sep 1998 00:55:37 -0400 (EDT)" References: X-Mailer: Mew version 1.92 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980917100844U.thomma@baynetworks.com> Date: Thu, 17 Sep 1998 10:08:44 -0700 From: Tamiji Homma X-Dispatcher: imput version 971024 Lines: 23 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I had another soft updates panic today on my pre-CAM kernel, which I had > believed to be stable (it has Luoqi's patch and made it through several > world builds). > panic: initiate_write_filepage: dir inum 0 != new 246465 Just a data point. 9/16/1998 8pm PDT cvsup'ed. SMP(440FX, dual PPros, 128MB), SOFTUPDATES, SCSI_CAM(Single 4.3G 9ES), ELF make -j4 buildworld 1:20:39 successful make -j8 buildworld the same panic as above This is off topic but everytime I got panic and fsck with softupdate doesn't fix the file system correctly. I always have to turn softupdates off, and tunefs -n enable again after fsck. I remember that fsck is(must be?) softupdates aware so that it knows how to fix the file system inconsistency for softupdates enabled file system in case of crash. However, fsck appears to be not doing the job. Am I misunderstood about this? Tammy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message