Arch Linux

Description: I've noticed today that mounting a FAT32 volume I have, veracrypt now requires the option --fs-options=utf8=no to show all characters correctly. I'm 100% positive, I've changed nothing in the volume at all (for months). My volume is encoded with iso8859-1 charset.

If I issue "mount" in a console I get:

/dev/mapper/veracrypt1 on /home/musikolo/stuff type vfat (rw,relatime,uid=1000,gid=100,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,uft8,errors=remount-ro)

when I pass the abovementioned switch "--fs-options=utf8=no", the mount point looks like:
/dev/mapper/veracrypt1 on /home/musikolo/stuff type vfat (rw,relatime,uid=1000,gid=100,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)

which shows all characters correctly.

In an attempt to find out the root cause, I've tried rolling back my Linux kernel from 4.14.6 to 4.14.5, same as all the packages I upgraded within the last 3 days (from 18th back to 15th). Unfortunately, the issue was still there. I could not roll back more days, because I recently upgraded my to plasma 17.12, and there are too many packages (14th). You can see all the packages I've recently upgraded at https://pastebin.com/g6H3Lcmf

It took my a long while to figure out how to workaround the issue, but I would like to know the root cause of it.

Any clue on what could have changed the previous behavior?

More info - using:
veracrypt 1.21-2
fuse-common 3.2.1-1 (also tried with 3.2.0-1)
linux 4.14.6 (also tried with 4.14.5)