From owner-freebsd-current Thu Jun 22 22:24:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (fw2.aub.dk [195.24.1.195]) by hub.freebsd.org (Postfix) with ESMTP id 3296D37B5F5; Thu, 22 Jun 2000 22:24:05 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id HAA00671; Fri, 23 Jun 2000 07:23:49 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Peter Wemm Cc: Adrian Chadd , Julian Elischer , Anders Andersson , cvs-all@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/contrib/softupdates softdep.h ffs_softdep.c In-reply-to: Your message of "Thu, 22 Jun 2000 16:43:00 PDT." <20000622234300.2BB821CD7@overcee.netplex.com.au> Date: Fri, 23 Jun 2000 07:23:49 +0200 Message-ID: <669.961737829@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000622234300.2BB821CD7@overcee.netplex.com.au>, Peter Wemm writes : >Because fsck is supposed to be able to do things more intelligently when it >knows the *previous* mount state, not the current state. ie: if a disk was >last mounted in softupdates mode, fsck is supposed to do stuff differently >(possibly doing as little as a superblock cleanup and deferring the >lost-space recovery until much later). > >For the NetBSD version to work, what needs to happen is that the -osoftdep >flag needs to be propagated to the superblock so that after reboot, fsck >knows what to do. When it is next mounted, then update it to the new state. Right, but if mounting with -osoftdep, does what a "tunefs -n enable" does (and vice versa) fsck will have that knowledge and the tunefs step would be un-needed. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message