From owner-freebsd-current Wed Jul 15 18:41:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22311 for freebsd-current-outgoing; Wed, 15 Jul 1998 18:41:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22305 for ; Wed, 15 Jul 1998 18:41:06 -0700 (PDT) (envelope-from rock@wurzelausix.cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.0/1998052000) with ESMTP id DAA18102 for ; Thu, 16 Jul 1998 03:40:57 +0200 (CEST) Received: from gate.ics (acc1-176.telip.uni-sb.de [134.96.113.176]) by cs.uni-sb.de (8.9.0/1998060300) with ESMTP id DAA24886 for ; Thu, 16 Jul 1998 03:40:56 +0200 (CEST) Received: from doom.ics (doom.ics [192.168.0.254]) by gate.ics (8.9.0/1998061600) with ESMTP id DAA14588 for ; Thu, 16 Jul 1998 03:39:47 +0200 (CEST) Received: (from rock@localhost) by doom.ics (8.9.0/1998061600) id DAA00399; Thu, 16 Jul 1998 03:45:17 +0200 (CEST) From: "D. Rock" MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Thu, 16 Jul 1998 03:45:17 +0200 (CEST) To: current@FreeBSD.ORG Subject: Re: softupdates and / In-Reply-To: <13740.63488.73527.611486@doom.ics> References: <199806231530.LAA00998@lor.watermarkgroup.com> <13740.63488.73527.611486@doom.ics> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13741.22887.960238.966148@doom.ics> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Luoqi Chen writes: > > > Hi, > > > > > > I had some (hardware related) crashes lately and noticed that > > > softupdates arenīt enabled if the filesystem was unclean. So after a > > > crash I had to boot twice to re-enable softupdates on / again (no need > > > to run tunefs though). > > > Is this because soft updates are no mount option and so cannot be > > > enabled later and soft updates arenīt enabled on an unclean fs for > > > safety reasons? > > > Or is this just a bug? > > > > > > Daniel > > > > > I believe this is a bug. After fsck fixes inconsistencies on the disk, > > it will remount / with MNT_RELOAD flag to update the in-core superblock > > image. For some reason, fsck might change fs_ronly flag in superblock > > (to be more precise, it will change fs_ronly iff it has fixed the free > > block count -- could any more knowledgeable person tell me why it is > > doing that?!), and because of that, all the code to be called during > > ro->rw update is bypassed, including enabling of softupdate. F'upd my own mail. I just forgot to mention: At least 2 times, after a crash, the root fs was noted "clean" during the reboot (but not my other UFS partition) and no fsck required (and now of course with soft updates enabled). I didn't trust the information (does the superblock gets updated while being mounted or does it have a "stable" flag similar to Sun's UFS?)After rebooting again in single user mode and doing a forced fsck of / an error was indeed found ("LINK COUNT INCREASING"). Probably it wasn't more because the system was almost idle while it crashed. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message