[FAT] mkfs: File name too long

[diver]

hrev57972

dd if=/dev/zero of=1g.img bs=1 count=0 seek=1G
0+0 records in
0+0 records out
0 bytes copied, 5.7e-05 s, 0.0 kB/s

~> mkfs -t fat test.img

About to initialize test.img with FAT32 File System
Are you sure you want to do this now?

ALL YOUR DATA in test.img will be lost forever.
Continue (yes|[no])? yes
DiskDeviceJobQueue::Execute(): executing job: N8BPrivate13InitializeJobE
DiskDeviceJobQueue::Execute(): executing job failed: File name too long
mkfs: Initialization of "Unnamed Image" failed: File name too long

syslog:

KERN: intel: ep_std_ops(0x1)
KERN: intel: ep_std_ops(0x2)
KERN: intel: pm_std_ops(0x1)
KERN: intel: pm_identify_partition(454, 4: 0, 104857600, 512)
KERN: intel: pm_std_ops(0x2)
KERN: identify(454, 0xffffffff8b452d80)
KERN: exfat: invalid superblock!
KERN: btrfs: [1734877858:  1969] invalid superblock!
KERN: ufs2: Invalid superblock! Identify failed!!
KERN: ntfs: error: identify_partition: boot signature doesn't match
KERN: ext2: invalid superblock!
KERN: dosfs_initialize(454, , 'Unnamed Image', '<NULL>', 104857600)

[madmax]

Not a bug?

FAT's volume label is limited to 11 characters, so the default 'Unnamed Image' for image files doesn't fit. Just pass a valid FAT volume label to mkfs: mkfs -t fat test.img TESTIMG.

The error message could be more clear, though.

[diver]

Indeed, I didn't realise it was a label limitation. So either error message should be changed or the volume label itself should be different (in case of FAT).