On /dev/md2 I created exFAT filesystem (on whole device).
The gpart(8) tool interprets (incorrectly) that as MBR:
# gpart show md2
=> 63 2097089 md2 MBR (1.0G)
63 2097089 - free - (1.0G)
The fstyp(8) tool correctly shows its exFAT:
# fstyp -u /dev/md2
For the record file(1) is also wrong:
# file -s /dev/md2
/dev/md2: DOS/MBR boot sector
This is on 12.1-BETA2 system.
gpart(8) is used to manage partition tables. exFAT is filesystem, not a partition table.
But its a lie, its not a MBR partition table there = bug.
exFAT filesystem has boot sector, that contains MBR's signature:
When you create exFAT filesystem on a raw disk, it automatically creates MBR partition table.
So gpart should show exFAT/MBR label then?
+1 to everything ae@ has already mentioned.
exFAT (FAT in general) has a DOS MBR boot block at the beginning of the filesystem image. gpart is for managing partitions.
I understand the confusion, but printing "MBR" when an MBR header is present is a broadly reasonable interpretation of a FAT filesystem header by a tool looking for MBR or GPT partitions. I'd suggest not putting filesystems on unpartitioned disks, or just not invoking gpart on unpartitioned disks.
file(1) is contrib code, there's some upstream a bug can be reported at.
Ok, your system, your choice.