Unable to access certain files on NTFS share

jschiwal · 06-30-2006, 03:58 AM

From the man mount manpage:

Code:

Mount options for ntfs
       iocharset=name
              Character  set  to  use when returning file names.  Unlike VFAT, NTFS suppresses names that contain unconvertible charac‐
              ters. Deprecated.

       nls=name
              New name for the option earlier called iocharset.

       utf8   Use UTF-8 for converting file names.

       uni_xlate=[0|1|2]
              For 0 (or `no' or `false'), do not use escape sequences for unknown Unicode characters.  For 1 (or `yes' or `true') or 2,
              use vfat-style 4-byte escape sequences starting with ":". Here 2 give a little-endian encoding and 1 a byteswapped bigen‐
              dian encoding.

       posix=[0|1]
              If enabled (posix=1), the file system distinguishes between upper and lower case. The 8.3 alias names  are  presented  as
              hard links instead of being suppressed.

       uid=value, gid=value and umask=value
              Set  the  file permission on the filesystem.  The umask value is given in octal.  By default, the files are owned by root
              and not readable by somebody else.

The gid option that you used was fine. I use both a uid= and gid= option. The charset used result in some very evil characters. I think that you need to use both the nls= option and the iocharset option. I believe that the nls= option should be the charset that you want the filename characters translated to, while the iocharset option needs to match the charset of the filenames that exist on the partition. The trick is figuring out what that would be. It is possible also that these filenames contain control characters for some unimaginable stupid reason. ( Why do people post messages in caps, use evil characters like ()*![]{} in filenames, put spaces in directory names, or use the stupidly redundant "My " in front of directory names, use black backgrounds and unreadable foreground colors? )

However, from your first listing, It look like there is a problem with the filesystem, or this is a strange version of NTFS that linux doesn't understand. You might consider burning these files and reformatting the partition fresh.

Ashrack · 06-30-2006, 06:29 AM

Quote:

Originally Posted by haertig

Quote:

You could also try using "Captive NTFS" to mount the partition. This uses NTFS drivers Linux finds in the Windows installation for file access, rather than the NTFS drivers installed into Linux itself. Captive NTFS should be installable on your distro.

with captive it works. but thats no sollution 4M since its so slooow.

Ashrack · 06-30-2006, 06:55 AM

Quote:

Originally Posted by jschiwal

I think that you need to use both the nls= option and the iocharset option. I believe that the nls= option should be the charset that you want the filename characters translated to, while the iocharset option needs to match the charset of the filenames that exist on the partition. The trick is figuring out what that would be. It is possible also that these filenames contain control characters for some unimaginable stupid reason.

I doubt that illegal characters are responsible. Because if U look at this file:

Code:

?--------- ? ?    ?       ?                ? test.txt

U can see that it possess no threat for ascii table and is even compatible with dos filename(8+3)

Quote:

However, from your first listing, It look like there is a problem with the filesystem, or this is a strange version of NTFS that linux doesn't understand. You might consider burning these files and reformatting the partition fresh.

The NTFS FS was created with Win2003 SP1 server and has 64kb CLUSTER SIZE and is around 200GB in size. So reformating the partition is out of the question... This partition is mainly used for DIVX movies. And eventually I will be moving all of this to XFS partition if I set up UBUNTU DAPPER as a server properly.

mikieboy · 06-30-2006, 07:13 AM

I'm probably talking crap here, but is it possible these movie files are copyright protected?

Ashrack · 06-30-2006, 07:19 AM

nope! and as U can see from my previous post that a file called:
'test.txt'
has the same problems

Ashrack · 06-30-2006, 08:04 AM

Apperantly I have already found the sollution. The NTFS version in the 2.6.15 kernel is too old.
Further info here:
http://forum.linux-ntfs.org/viewtopic.php?t=344

mikieboy · 06-30-2006, 02:23 PM

Glad to hear you got it sorted. Amazing to hear that 2.6.15 is already showing its age!

haertig · 06-30-2006, 04:31 PM

Quote:

Originally Posted by Ashrack

The NTFS version in the 2.6.15 kernel is too old.

Wow. 2.6.15 hasn't been around very long. Has a new version of NTFS come out that recently? I know Microsoft tweaks the NTFS unpublished spec with most new variants of Windows, but I didn't know anything new in NTFS had come out that recently. I have no trouble reading NTFS with my 2.6.14 kernel, but that is NTFS as implemented in XP Home, XP Pro, and W2k. I'll definitely keep my kernel version in mind if I run into any NTFS problems in the future.

Ashrack · 07-01-2006, 07:26 AM

MIKIEBOY
My thoughts exactly!

HAERTIG
Apperantly the old NTFS code wasnt compatible with 200GB partition w/ 64kb cluster size and its sparse files.
Anyway I've compiled kernel 2.6.17 with con kolivas server patchset and everything flies.
I will probably be coverting my big old NTFS partition soon to XFS when I sort out the final problem with FREENX