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

Soukyuu · 2015-03-26 13:28:37

..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)

R00KIE · 2015-03-26 13:52:00

Since you are using ntfs I suppose you have access to a machine running windows, I would try to do a complete disk check on windows and see if that solves the problem.

Soukyuu · 2015-03-27 13:04:02

I do, it's a dualboot system (first in my sig). I've scanned the drives and there were no errors on winsys. There were some errors on windata which it fixed, but the error is still there. I did scan the drive again after fixing to make sure the errors are really gone.
Also, 'find' still only lists files on winsys with that inode number.

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?

R00KIE · 2015-03-27 16:27:38

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).

Soukyuu · 2015-03-27 21:44:57

Hmm, it appears there was an old, duplicate recycle bin entry in the $RECYCLE.BIN folder from a previous windows installation. Entering the folder triggered the journal message. While empty on linux, it did appear on windows, but I didn't have access rights. After gaining them ("you don't have a rights, want them?" sure does sound like a secure system, doesn't it? -_-), the folder still appeared empty, but was about 1GB in size. Because I couldn't see any files in there, I just deleted the whole thing and now the message is gone. I'm thinking that maybe the "second" recycle.bin was confusing ntfs-3g, or maybe one of the files in there was somehow corrupted - yet chkdsk didn't care.

I wish I could just transfer those NTFS volumes to some linux format, but that ain't happening yet. Thanks for the hints.

Last edited by Soukyuu (2015-03-27 21:46:19)

Arch Linux

#1 2015-03-26 13:28:37

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

#2 2015-03-26 13:52:00

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

#3 2015-03-27 13:04:02

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

#4 2015-03-27 16:27:38

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

#5 2015-03-27 21:44:57

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

Board footer