From owner-freebsd-current Wed Jun 5 7:36:58 2002 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 2E67637B400 for ; Wed, 5 Jun 2002 07:36:54 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.3/8.12.2) with ESMTP id g55EZRCd050844; Wed, 5 Jun 2002 16:35:37 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Andrew Kenneth Milton Cc: current@FreeBSD.org Subject: Re: Please test the UFS2 patch! In-Reply-To: Your message of "Thu, 06 Jun 2002 00:31:45 +1000." <20020606003145.C74184@zeus.theinternet.com.au> Date: Wed, 05 Jun 2002 16:35:27 +0200 Message-ID: <50843.1023287727@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20020606003145.C74184@zeus.theinternet.com.au>, Andrew Kenneth Milton write s: >+-------[ Poul-Henning Kamp ]---------------------- >| >| Yes, if you just drop it in, nothing should change much after all. >| >| You can then create ufs2 filesystems with "newfs -O 2" and start to >| beat up the new code for good. > >Is it helpful to test this via md type mounts, or only on physical media >right now? Any testing is helpful, no matter how its done, but of course if you can think of some way to test it which nobody else does, it will be much more interesting. There are many tests of that sort you can do with md(4) mounts, for instance beating on dump/restore... -- 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