[Tux3] mkfs.tux3: wiping other fs signatures

OGAWA Hirofumi hirofumi at mail.parknet.co.jp
Sat Dec 13 07:36:25 PST 2008

Szabolcs Szakacsits <szaka at ntfs-3g.org> writes:

>> > Ah, I was forgetting about it. I think, first 1024bytes (FAT, NTFS, and
>> > EFI), and last 64kbytes (EFI, and MD RAID), should be enough. Right?
>> Please, let us be on the safe side, and do the first 256k or even 1M each.
>> FAT stores a backup boot sector, and that is typically in the 11th sector, but
>> it can be nearly anywhere else.
>> So I'd beg for the minimum of 64kB at start at end - and if it doesn't cost
>> too much, please 1M.
> Afair, reiserfs puts signature at 128 kB. NTFS may also have a backup at 
> the middle of the volume.

I see. Well, auto detection is not perfect always, rather it's mess

However, if zeroed the boot sector is not enough for NTFS, in theory, we
can't detect NTFS even if it's FAT actually?  Because the middle of the
volume may be data block on FAT. So, we can't do anything for it.
Instead, NTFS driver or auto-detect engine have to do something, if it

Anyway, the solution for auto-detection would change the detection
order, i.e. try to detect tux3 before reiserfs and NTFS.  Because tux3
put superblock at 4096 offset for now, and other blocks can be used for
any purpose.

So I think, mkfs clears first 1024b (or 4096b) and last 64kb, at least
for now, it is enough?

OGAWA Hirofumi <hirofumi at mail.parknet.co.jp>

Tux3 mailing list
Tux3 at tux3.org

More information about the Tux3 mailing list