Re: NTFS drive with [ ] in filename... How to access?




"Michael C." <mjchappell@xxxxxxxxxxx> wrote in message
news:Zsioi.2456$jC4.75@xxxxxxxxxxx
On Fri, 20 Jul 2007 21:06:28 GMT,
Noozer <dont.spam@xxxxxxx> wrote:
Starseed wrote:

Noozer wrote:
I have a USB drive. The drive has several directories, many who's name
contain square brackets. I do this to catagories my directories. i.e.
"[Games]", "[Imaging]".

When I mount the drive in Linux (OpenSUSE 10.2) I can see all the
files
and directories, except those using the square brackets. I tried
creating
a few directories on my desktop and Linux accepts them fine with
square
brackets.

Any idea why this is happening and how I can gain access to these
directories?

Hmm, have you tried the tab autocomplete in a terminal?

I should have clarified. This was using Konqueror.

I just tried to access the drive from the terminal and get some odd
results...

steve@suse:/media/500gSeagate> dir
ls: cannot access Archive: Input/output error
total 8
d????????? ? ? ? ? ? Archive
dr-x------ 1 steve root 4096 2007-06-06 04:48 Common Installation
Files
dr-x------ 1 steve root 0 2007-06-06 16:53 RECYCLER
dr-x------ 1 steve root 4096 2007-06-06 04:29 System Volume
Information
-r-------- 1 steve root 82 2006-09-23 17:08 USBDLM.ini
steve@suse:/media/500gSeagate> ls Archive
ls: cannot access Archive: Input/output error

...since the drive is removable, I don't have it included in fstab.
Mount
describes the drive like this...

/dev/sdc1 on /media/500gSeagate type ntfs (rw,nosuid,nodev,uid=1000)

...now I'm thinking that it's just a coincidence about the square
brackets
and it might be a permissions issue, but I don't know enough to verify
this.

I don't play with NTFS often, but iirc there are options to compress
or encrypt directories in NTFS. Can you access those directories in
Windows. I don't believe the NTFS driver in Linux cares about the
NTFS permissions, but I don't know if it handles compressed or
encrypted directories.

Definately not an encrypted drive or a permissions issue. I think that this
is a filesystem error and will be "recovering" the data ASAP.


.



Relevant Pages