From owner-freebsd-current Wed Mar 28 7:25:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 338E337B71C for ; Wed, 28 Mar 2001 07:25:44 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f2SFPZ395546; Wed, 28 Mar 2001 17:25:35 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Chris Dillon Cc: current@FreeBSD.ORG, kirk@mckusick.com Subject: Re: fsck pass sanitizing patch In-Reply-To: Your message of "Wed, 28 Mar 2001 09:05:09 MDT." Date: Wed, 28 Mar 2001 17:25:35 +0200 Message-ID: <95544.985793135@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Chr is Dillon writes: >On Wed, 28 Mar 2001, Poul-Henning Kamp wrote: > >> There is no way to tell it that ccd0c overlaps ad0 and ad1. >> >> With the patch, it will do it this way: >> >> pass 2: >> One process doing ad0s1e >> One process doing ad1s1e and ad1s1f >> >> and when they are complete: >> >> pass 11: >> One process doing ccd0c > >I've always assigned a ccd (this would apply to Vinum volumes as well, >I'd think) a pass number of 1. Pass number 1 in magic in that it is sequential. Traditional wisdom (or lack thereoff) have only put rootfs in pass 1. Until my patch, pass 1 would certainly be better for ccd than pass > 1. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | 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