trouble accessing directory with quotes in read-only mode

Bug #129542 reported by Ori Avtalion
4
Affects Status Importance Assigned to Milestone
ntfs-config
Invalid
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Using feisty amd64.

When mounting an ntfs drive with read-only support, I cannot access/modify directories that have quotes (") in their name.

To test:
1) Mount a drive with enabled write support.
2) Create a directory called "foo" (with the quotes).
3) Unmount the drive and mount it again without write support.
4) Try accessing the dir, renaming it, ls -l'ing it to get info - nothing will work.

When mounted in read-only mode, the /etc/fstab flags are "umask=222,utf8".
When mounted with write enabled, the flags are "defaults,locale=en_US.UTF-8"

Is it possible that the problem is caused due to the locale not being specified?

Revision history for this message
Florent Mertens (givre) wrote :

This seams to be a problem with the ntfs kernel driver.
Files with quotes can be access correctly with both ntfs-3g & ntfs-fuse,
but not with the ntfs kernel driver

Changed in ntfs-config:
status: New → Invalid
Revision history for this message
Ori Avtalion (salty-horse) wrote :

I think this is fixed in gutsy.
When disabling write support from the ntfs-config tool, /etc/fstab uses the "ntfs" driver with "umask=222,utf8".
With that configuration, I can read files and directories with quotes in their names.

description: updated
Revision history for this message
Ralph Janke (txwikinger) wrote :

Thanks for submitting this report.

Due to the fact that the problem does not occur in a released kernel, is it ok to close this report?

Thanks.

Changed in linux-source-2.6.20:
assignee: nobody → txwikinger
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

This appears to have been resolved against Gutsy so marking "Fix Released" against 2.6.22. Against 2.6.20 this will be closed as it does not qualify for a stable release update. Thanks!

Changed in linux-source-2.6.22:
status: New → Fix Released
Changed in linux-source-2.6.20:
status: Incomplete → Won't Fix
Ralph Janke (txwikinger)
Changed in linux-source-2.6.20:
assignee: txwikinger → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.