I got a reply from Larry Osterman, with the word that it's a bug in CHKDSK (unfortunately there's no "deeper" help with other reserved characters, though):
On Thu, 13 Mar 2008 10:15:14 -0700, Larry Osterman <[EMAIL PROTECTED]> wrote: > From one of the NT filesystem developers (and yes, I filed the bug against > chkdsk): > > ----- > > I'm assuming you mean in a directory search. As far as I know, NTFS does not > do anything. A name with a '?' is not valid, so you cannot try to access the > file. If the file already exists, it would show up in a directory listing, > but you would have no way to delete or rename it. > > To the direct point below, 0x3F is explicitly reserved as a wild card for > NTFS on Windows and is explicitly blocked from being used in a file name. If > someone is implementing the NTFS file system on a different OS, they could > choose to make 0x3F a valid character, but that would not be compatible with > NTFS on Windows. > > I also agree with the assessment that this is a bug in chkdsk. > ----- > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 12, 2008 9:30 PM > To: Larry Osterman > Subject: (Larry Osterman's WebLog) : NTFS, POSIX, CHKDSK and filename > character compat > Importance: High > > > Hi Larry, > > Sorry to be sending this to you as a visible Windows guy, but perhaps you can > point me in the right direction? > > We're having a bit of a tiff on the Linux NTFS-3G mailing list over NT > compatibility. The maintainers hold that creating filenames with '?' (0x3F) > characters in them is within the NTFS spec since the fact that CHKDSK doesn't > complain, it's therefore ok, while I (holding a torch for other folks on the > forums that have been burned by this issue) maintain that since the POSIX > subsystem (now known as Interix, SFU etc., and by expectation the one that > should maximize POSIX behaviour of the filesystem) converts 0x3F in filenames > into 0xF03F, that NTFS-3G should follow suit. > > The basic problem is that even though CHKDSK doesn't complain about > characters containing '?', such files can't even be deleted, much less > created or modified, whether using the Win32 subsystem or PSXDLL.DLL and > thence direct to NTDLL.DLL. > > I'm of the opinion that since the files in question can't be managed from NT, > the fact that they're not flagged by CHKDSK should probably be regarded as a > CHKDSK bug. These files could be of a substantial size, but short of > reformatting there would be no way from NT to free up the space. > > Anything you can do for us would be greatly appreciated, > > Thanks, > > -- Barry > ---------------------------------- > This message was generated from a contact form at: > http://blogs.msdn.com/larryosterman/default.aspx > It was submitted by barrkel ([EMAIL PROTECTED]) > > Your contact information was not shared with the user. -- Barry -- http://barrkel.blogspot.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ ntfs-3g-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
