Date: Thu, 17 Sep 1998 10:08:44 -0700 From: Tamiji Homma <thomma@BayNetworks.COM> To: ben@rosengart.com, benedict@echonyc.com Cc: current@FreeBSD.ORG Subject: Re: soft updates panic once more; downgrading Message-ID: <19980917100844U.thomma@baynetworks.com> In-Reply-To: Your message of "Thu, 17 Sep 1998 00:55:37 -0400 (EDT)" <Pine.GSO.4.02.9809170051550.14188-100000@echonyc.com> References: <Pine.GSO.4.02.9809170051550.14188-100000@echonyc.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980917100844U.thomma>