Ark hangs when file/directory name on NTFS contains a colon
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| firefox (Ubuntu) |
Confirmed
|
Wishlist
|
Unassigned | ||
| kdeutils (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
| ntfs-3g (Ubuntu) |
Invalid
|
Low
|
Unassigned | ||
Bug Description
What I did:
- I installed Kubuntu 8.04 (I always update when Adept_updater suggests it) in parallel with WinXPSP2, which is installed on NTFS partitions.
- I used Firefox to save some webpages directly on a NTFS partition. These webpages had colons (":") in their title so FF used that as file/directory names. I justed clicked on "save".
- I right-clicked the directory where I saved all these files an chose compress to ZIP.
- The Ark status windows comes. It seems like it is proceeding (the rectangle in the bar goes from the left to the right and back all the time) but the hard-drive doesn't do anything.
In Windows, 7zip says that it can't open that directories. However, I can see them in the Windows Explorer but I can't rename them there. I have to do that in Kubuntu. When I have removed the colons there by renaming, everything works as it should.
As far as I know, NTFS internally uses a colon to seperate the (hidden) ADS part from the rest of the filename.
I know that Linux and MS are completely different worlds, but in my opionion as user:
- NTFS-3G shouldn't allow colons in filenames.
- Applications like Firefox shouldn't suggest names with colons (or should have at least an option in the settings to change that)
- Ark should abort trying to open these files and notify me.
| Changed in kdeutils: | |
| importance: | Undecided → Wishlist |
| Changed in firefox-3.0: | |
| importance: | Undecided → Low |
| Changed in kdeutils: | |
| importance: | Wishlist → Low |
| Changed in ntfs-3g: | |
| importance: | Undecided → Low |
| Szabolcs Szakacsits (szaka) wrote | #1 |
| Jonathan Thomas (echidnaman) wrote | #2 |
| Changed in ntfs-3g: | |
| status: | New → Invalid |
| Changed in kdeutils: | |
| status: | New → Fix Released |
| Changed in firefox-3.0: | |
| importance: | Low → Wishlist |
| Jonathan Thomas (echidnaman) wrote | #3 |
| Thomas Hotz (thotz-deactivatedaccount) wrote | #4 |
| affects: | firefox-3.0 (Ubuntu) → firefox (Ubuntu) |
| Changed in firefox (Ubuntu): | |
| status: | New → Confirmed |
http://
Why does the driver allow special characters in the filenames?
NTFS supports several filename namespaces at the same time: DOS, Win32 and POSIX. While the NTFS-3G driver handles all of them, it always creates new files in the POSIX namespace for maximum portability and interoperability reasons. This means that filenames are case sensitive and all characters are allowed except '/' and '\0'. This is perfectly legal on Windows, though some application may get confused. If you find so then please report it to the developer of the relevant Windows software.
Workaround: If case insensitivity handling and/or restriction of special character usage is desirable then you may export the NTFS volume via Samba which supports this functionality the same way as it does for other POSIX file systems.
Status: Not NTFS-3G problem.