From owner-freebsd-fs Fri Jan 31 10:51:27 2003 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2E2B37B401 for ; Fri, 31 Jan 2003 10:51:25 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1511543F9B for ; Fri, 31 Jan 2003 10:51:25 -0800 (PST) (envelope-from phk@freebsd.org) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id h0VIpO4W019188; Fri, 31 Jan 2003 19:51:24 +0100 (CET) (envelope-from phk@freebsd.org) To: Steve Byan Cc: freebsd-fs@freebsd.org, tech-kern@netbsd.org Subject: Re: DEV_B_SIZE From: phk@freebsd.org In-Reply-To: Your message of "Fri, 31 Jan 2003 13:41:35 EST." Date: Fri, 31 Jan 2003 19:51:24 +0100 Message-ID: <19187.1044039084@critter.freebsd.dk> Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message , Steve Byan writes : >> The only thing that exposes us to risk is we don't know the risk >> exists, so as long as the fact that a 4k physical sector size is >> used is not hidden from us, we can adapt. > >But would existing code be functionally broken (perhaps with respect to >failure recovery) if it were to not be modified to adapt to a different >physical block size? Not broken any worse than because of write-caching. >> Nope. > >Really? fsck can recover from losing 4K bytes surrounding the last >metadata block written? If the fragment size is 4k when the filsystem is created, and this would happen automatically, then there is no window for lossage. The thing we really need is working tagged-queing... -- 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-fs" in the body of the message