Summary: | gpart(8) detects exFAT fs as MBR | ||
---|---|---|---|
Product: | Base System | Reporter: | Slawomir Wojciech Wojtczak <vermaden> |
Component: | bin | Assignee: | freebsd-bugs (Nobody) <bugs> |
Status: | Closed Not A Bug | ||
Severity: | Affects Many People | CC: | ae |
Priority: | --- | ||
Version: | 12.1-RELEASE | ||
Hardware: | Any | ||
OS: | Any |
Description
Slawomir Wojciech Wojtczak
2019-10-02 08:37:50 UTC
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: http://elm-chan.org/docs/exfat_e.html 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. Regards, vermaden |