> On Wed, 12 Mar 2008, Szabolcs Szakacsits wrote: > > > Sorry but I meant to create the files on Linux. What you have found is > > the expected, correct behaviour in the WIN32 namespace and documented for > > instance here: > > > > http://www.reddragonfly.org/ntfs/concepts/filename_namespace.html > > > > I expect CHKDSK not to warn when the files are created on Linux, i.e. we > > don't have the submitted problem. > > I tried and CHKDSK has no problem with these file names.
I wonder how you know that CHKDSK has no bugs itself? Considering the implications, I believe this is more likely than a kernel bug. > Btw, what I have meant under "submitted problem" was NTFS compatibility > (NTFS does no Unicode normalization). I'm aware Microsoft has also Unicode > problems (hint: search Microsoft employees' blogs). If they can't read a > valid POSIX filename what CHKDSK accepts then they should fix their > software. By fixing CHKDSK? It may be a good idea. I'll get on that end too. I believe it's a CHKDSK problem because the file system space occupied by such files can't be reclaimed from within NT except by reformatting the partition. -- 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
