You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems like the special volume label file is actually required in some cases (and you just discovered one of them 🎉). I was under the impression that the special file is optional - at least with FAT16/32 I cannot remember that fsck ever complained about it. file and fatcat seem to work just fine without it, but lsblk/Linux is a bit more picky. 🙂
As a workaround you can add a new FATDirectoryEntry to the root directory with the FATDirectoryEntry.ATTR_VOLUME_ID set as an attribute. I'll need to investigate under which circumstances the special file is actually required first.
Attempting to create a volume using the new mkfs() function:
It appears that on mounting, the volume label is not set:
I get the same results with FAT16/32
A similarly created file using mkfs yields a label:
$ mkfs.fat -C -F12 -n "TSTLABEL" test_mkfs.fat12 256 $ sudo losetup /dev/loop0 ./test_mkfs.fat12 $ lsblk -o name,label,size,uuid NAME LABEL SIZE UUID loop0 TSTLABEL 256K A562-5D4B
The text was updated successfully, but these errors were encountered: