[Solved] [ntfs-3g] Filename decoding failed: Invalid or incomplete...

Question

..multibyte or wide character. I have this message pop up every few minutes in my journal.
ntfs-3g is up to date, 2014.2.15-1
/mnt is where every ntfs drive is mounted, searching for this inode gives me
$ find /mnt/ -inum 378576
/mnt/winsys/Windows/servicing/Packages/Package_184_for_KB2994290~31bf3856ad364e35~amd64~~6.3.1.3.cat
/mnt/winsys/Windows/System32/catroot/{F750E6C3-38EE-11D1-85E5-00C04FC295EE}/Package_184_for_KB2994290~31bf3856ad364e35~amd64~~6.3.1.3.cat
/mnt/winsys/Windows/WinSxS/Catalogs/6e717cab8a384f3ddad041ba1bf0bf956d38cb7a6d4f0482f253439fc11ae49d.cat
volumes are mounted with defaults + uuid and user-mountable
UUID=DEEA3A44EA3A196B /mnt/winsys ntfs-3g uuid=myuser,gid=users 0 0
How can I fix that?
Last edited by Soukyuu (2015-03-27 21:46:58)

Answer 1

Soukyuu wrote:If I run the search on /mnt/windata, I can see the inode error appear almost instantly.
Could it be that 'find' can't show the file affected because of the error?
That is possible. If windows thinks(1) there is no problem then my guess would be a filename with "uncommon" characters or violating some restriction. If reasonably feasable you could try keeping an eye on the output of dmesg while you use ls to list the contents of the directories on your windata partition, when you try to list the directory with the offending file(s) you should see errors. Then go to windows and rename the files if possible.
You might want to ask about this on the ntfs-3g mailing list, maybe you have caught some bug or corner case, and you might get some tips on how to deal with this.
(1) Windows is (or used to be) idiosyncratic, you have a set of restrictions on filenames, and usually you can't directly create files that violate the restrictions, however some programs may be able to get around those restrictions and create files that you will not be able to deal with via explorer, this might be one of those cases. If I'm not mistaken this has happened to me a few times (when I still used Windows regularly - WinXP days) and at the time checkdisk would say everything was fine but explorer would refuse to rename, move or delete the files. The workaround was to delete/rename the file with the program that created it, in one case it was winrar (the problem that time was a filename too long).