FAQ SearchLogin
Tuxera Home
View unanswered posts | View active topics It is currently Wed Aug 04, 2021 00:54



Post new topic Reply to topic  [ 3 posts ] 
File name that is invalid in Windows causes NTFS error 
Author Message

Joined: Thu Aug 11, 2011 08:59
Posts: 13
Post File name that is invalid in Windows causes NTFS error
Hello,
I am part of the Thunderbird development team. Here
https://bugzilla.mozilla.org/show_bug.cgi?id=1265153
someone reported that storing a mail message with Thunderbird on Linux on an NTFS volume causes NTFS file system errors.

I stored a file with this name:
[Bug 1265153] linux versions "save file" saves corrupted .eml files on ntfs.eml
onto an NTFS volume.

The reporter of the bug used an exclamation mark in the file name.

In my case I got the following CHKDSK error:

Deleted invalid filename [Bug 1265153] linux versions "save file" saves corrupted .eml files on ntfs.eml (53397) in directory 896043.
File 53397 has been orphaned since all its filenames were invalid
Windows will recover the file in the orphan recovery phase.
Correcting minor file name errors in file 53397.

CHKDSK "rescued" the file to found.000\file0000.chk.

Can you make sure that ntfs-3g sanitises filenames so they don't cause problems on Windows.

I was using Linux Mint 17.1 with ntfs-3g 2014.2.15.A3.3.


Sat Apr 16, 2016 20:58
Profile
NTFS-3G Lead Developer

Joined: Tue Sep 04, 2007 17:22
Posts: 1286
Post Re: File name that is invalid in Windows causes NTFS error
Hi,

Quote:
The reporter of the bug used an exclamation mark in the file name.

Please confirm, I have never seen exclamation marks rejected by Windows, and there may be other reasons (such as a dot as the last character).

The "windows_names" mount option was designed for users wanting to be prevented from creating file names they want to access on Windows :

Code:
       windows_names
This  option prevents files, directories and extended attributes
to be created with a name not allowed by Windows, because

      - it contains some not allowed character,
      - or the last character is a space or a dot,
      - or the name is reserved.

The forbidden characters are the nine characters " * / : < > ? \
| and those whose code is less than 0x20, and the reserved names
are CON, PRN, AUX, NUL, COM1..COM9, LPT1..LPT9, with  no  suffix
or followed by a dot.


Regards

Jean-Pierre


Sun Apr 17, 2016 08:20
Profile

Joined: Thu Aug 11, 2011 08:59
Posts: 13
Post Re: File name that is invalid in Windows causes NTFS error
Thank you for your quick reply. Much appreciated. And sorry for not reading the documentation at http://www.tuxera.com/community/ntfs-3g-manual/

jpa wrote:
Please confirm, I have never seen exclamation marks rejected by Windows, and there may be other reasons (such as a dot as the last character).


I cannot confirm that. Exclamation mark works, there must have been another reason. Sorry for repeating what was reported to us without verifying it myself.

Case closed. Thank you so much once again.


Sun Apr 17, 2016 08:41
Profile
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 3 posts ] 


Who is online

Users browsing this forum: Majestic-12 [Bot] and 5 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Original forum style by Vjacheslav Trushkin.