From owner-freebsd-current@FreeBSD.ORG Sat Oct 8 08:18:56 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1DD01106566B; Sat, 8 Oct 2011 08:18:56 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id CEA258FC0C; Sat, 8 Oct 2011 08:18:55 +0000 (UTC) Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id C1C215DAD; Sat, 8 Oct 2011 08:18:54 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.5/8.14.5) with ESMTP id p988IsWi032041; Sat, 8 Oct 2011 08:18:54 GMT (envelope-from phk@phk.freebsd.dk) To: Warren Block From: "Poul-Henning Kamp" In-Reply-To: Your message of "Fri, 07 Oct 2011 17:41:59 CST." Content-Type: text/plain; charset=ISO-8859-1 Date: Sat, 08 Oct 2011 08:18:54 +0000 Message-ID: <32040.1318061934@critter.freebsd.dk> Cc: freebsd-current@freebsd.org, Garrett Cooper , Glen Barber , "Andrey V. Elsukov" , Benjamin Kaduk , Arnaud Lacombe Subject: Re: aliasing (or renaming) kern.geom.debugflags X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Oct 2011 08:18:56 -0000 In message , Warren Block write s: >Since we're talking about this, could you review the usage in the >gmirror section of the Handbook GEOM chapter: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-mirror.html > >Seems like that is a valid non-debugging use, to allow the last block to >be written. gmirror and this procedure has several problems: 1. It steals the last sector on the disk. If that sector contained data you lost them, with no notice. Most often it will not, particularly on a freshly installed system, but it is still a bad thing. 2. The paritioning is not fixed up to record the stealing of this sector. I wouldn't be surprised if this could cause confusion down the road. 3. In this case, writing only happens to a single sector, which we assume is not going to be written by anybody else, so apart from #1 and #2 debugflags=16 does not cause any additional damage. This is the kind of usage that makes me sad I ever added that option. -- 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.