From owner-freebsd-current Wed Jul 15 11:53:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01015 for freebsd-current-outgoing; Wed, 15 Jul 1998 11:53:39 -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 LAA01006 for ; Wed, 15 Jul 1998 11:53:29 -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 UAA14892 for ; Wed, 15 Jul 1998 20:52:48 +0200 (CEST) Received: from gate.ics (acc2-212.telip.uni-sb.de [134.96.112.212]) by cs.uni-sb.de (8.9.0/1998060300) with ESMTP id UAA17761; Wed, 15 Jul 1998 20:52:46 +0200 (CEST) Received: from doom.ics (doom.ics [192.168.0.254]) by gate.ics (8.9.0/1998061600) with ESMTP id UAA09543; Wed, 15 Jul 1998 20:50:00 +0200 (CEST) Received: (from rock@localhost) by doom.ics (8.9.0/1998061600) id UAA13453; Wed, 15 Jul 1998 20:55:44 +0200 (CEST) From: "D. Rock" MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Wed, 15 Jul 1998 20:55:43 +0200 (CEST) To: current@FreeBSD.ORG, rock@cs.uni-sb.de Subject: Re: softupdates and / In-Reply-To: <199806231530.LAA00998@lor.watermarkgroup.com> References: <199806231530.LAA00998@lor.watermarkgroup.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13740.63488.73527.611486@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. [patch deleted] OK, I saw the patch being integrated into current. But still my root fs doesn't get soft updates enabled after a crash. This is my system booted after a forced crash: % mount /dev/sd0s1a on / (local, writes: sync 54051 async 62742) /dev/wd2a on /data (local, soft-updates, writes: sync 126 async 24454) procfs on /proc (local) /dev/wd0s1 on /dos (local) mfs:23 on /tmp (asynchronous, local, writes: sync 30 async 380) After a 2nd reboot, soft updated are enabled again, so the flag is on the on-disk copy of the superblock correct. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message