Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756348AbYBLX2J (ORCPT ); Tue, 12 Feb 2008 18:28:09 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751954AbYBLX1z (ORCPT ); Tue, 12 Feb 2008 18:27:55 -0500 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:39664 "EHLO sunset.davemloft.net" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1751536AbYBLX1y (ORCPT ); Tue, 12 Feb 2008 18:27:54 -0500 Date: Tue, 12 Feb 2008 15:28:26 -0800 (PST) Message-Id: <20080212.152826.243855481.davem@davemloft.net> To: jengelh@computergmbh.de Cc: chris.mason@oracle.com, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, btrfs-devel@oss.oracle.com Subject: Re: BTRFS partition usage... From: David Miller In-Reply-To: References: <20080212.001104.172517283.davem@davemloft.net> <200802120849.34477.chris.mason@oracle.com> X-Mailer: Mew version 5.2 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 711 Lines: 19 From: Jan Engelhardt Date: Tue, 12 Feb 2008 15:00:20 +0100 (CET) > Something looks wrong here. Why would btrfs need to zero at all? So that existing superblocks on the partition won't be interpreted as correct by other filesystems. It's a safety measure many mkfs programs use. > Superblock at 0, and done. Just like xfs. No, we won't do stupid things like that and make an entire cylinder of our disks unusable. See my other reply. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/