Date: Thu, 14 Feb 2008 02:51:47 +0200 (MET DST)
From: Szabolcs Szakacsits <szaka@ntfs-3g.org>
To: Jeff Garzik <jeff@garzik.org>
cc: David Miller <davem@davemloft.net>, chris.mason@oracle.com,
       jengelh@computergmbh.de, linux-kernel@vger.kernel.org,
       linux-fsdevel@vger.kernel.org, btrfs-devel@oss.oracle.com
Subject: Re: BTRFS partition usage...
In-Reply-To: <47B2517E.3080606@garzik.org>
Message-ID: <Pine.LNX.4.61.0802140145060.4561@dhcppc1>
References: <200802120849.34477.chris.mason@oracle.com>
 <Pine.LNX.4.64.0802121458420.21102@fbirervta.pbzchgretzou.qr>
 <200802120908.59602.chris.mason@oracle.com> <20080212.153329.98384016.davem@davemloft.net>
 <47B2517E.3080606@garzik.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1161
Lines: 27


On Tue, 12 Feb 2008, Jeff Garzik wrote:
> 
> Yep.  I chose 32K unused space in the prototype filesystem I wrote [1, 2.4
> era].  I'm pretty sure I got that number from some other filesystem, maybe
> even some NTFS incarnation.  

NTFS superblock (and the partial mirror copy) can be anywhere except in the 
first blocks. That space is where the $BOOT file is placed which contains 
the bootstrap code and the BIOS Paramether Block which includes the NTFS 
signature and describes various filesystem information needed to locate the 
superblock, etc.

Unlike mkfs.xfs which warns since at least 2002 and requires the -f option 
to override Sun disklabels, at the moment mkfs.ntfs will indeed destroy 
them. 

Thank you for the bug report and let's hope the next generation of Sun 
hardwares won't scatter the firmware too into random places inside a 
partition encoded by a fictitious size of disk cylinder.

	Szaka
--
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/