FS#16738 - Gnome 2.28 write to external hdd with NTFS

Attached to Project: Arch Linux
Opened by Ph.Philippov (br4) - Monday, 19 October 2009, 14:04 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 28 October 2009, 09:38 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I have an external hdd with NTFS, so i can't use the /etc/fstab (1)workaround and i don't think(actual know) "a symbolic link to the ntfs-3g binary" is a good idea for all cases.

So every time i want to write something i umount the hdd and then
mount /dev/sdxx /mnt/x/ -t ntfs-3g

Additional info:
Gnome 2.28
kernel26 2.6.31.4-1 x86_64

(1)see http://wiki.archlinux.org/index.php/Gnome_2.28_Changes#Volume_Manager
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 28 October 2009, 09:38 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in ntfs-3g 2009.4.4-2.
Comment by Federico Chiacchiaretta (baghera) - Monday, 19 October 2009, 15:20 GMT
AFAIK devicekit-disks uses directly udev, so would it be possible to fix this with udev rules?
Comment by Aaron Griffin (phrakture) - Monday, 19 October 2009, 19:48 GMT
I don't see a bug here. What are you reporting, a bug in a wiki page?
Comment by Ph.Philippov (br4) - Tuesday, 20 October 2009, 15:11 GMT
I can not override Gnome's ntfs settings to use ntfs-3g,so to automatic mount an external hdd with NTFS (with write permission) I'm left only with one workaround (or there is another but I can't find it, or someone to tell me) -> "a symbolic link to the ntfs-3g binary",witch as mention in HAL's wiki (1) :
"Possible issues using this method:
* if mount is called with the "-i" option it doesn't work
* possible issues with the kernel ntfs module "
(1)http://wiki.archlinux.org/index.php/HAL#The_last_resort
Comment by Aaron Griffin (phrakture) - Tuesday, 20 October 2009, 15:26 GMT
I'm fairly certain this is an upstream issue. I'll let Jan decide
Comment by Jan de Groot (JGC) - Wednesday, 21 October 2009, 07:23 GMT
Programs can pass additional mount options to devicekit-disks when mounting volumes. The valid mount options are hardcoded inside devicekit-disks, and some are prepended to the given options hardcoded also. The filesystem type is retrieved from udev, which is also hardcoded and not-overridable.

The fix here is to install a symlink for mount.ntfs in the ntfs-3g package. DeviceKit-disks uses mount -t ntfs to mount, so installing this symlink will make it use ntfs-3g.

As for HAL: HAL is history and has nothing to do with GNOME anymore.
Comment by Ph.Philippov (br4) - Wednesday, 21 October 2009, 12:47 GMT
As ntfs-3g file system developers will not put that (1) symlink it is up to Arch-ntfs-3g maintainer to decide ?
(1) http://www.tuxera.com/community/ntfs-3g-faq/#plugandplay
Comment by Kurt Marasco (celilo) - Wednesday, 28 October 2009, 00:17 GMT
This appears to be a gnome bug because in gconf under "/system/storage/default_options/ntfs/fstype_override" my key is set to "ntfs-3g".

The explanation for this key is:

The name of the file system driver to use by default when 'ntfs' is detected. This is useful for configuring the system to use the 'ntfs-3g' driver for all 'ntfs' file systems by default. User can still choose to use the 'ntfs' file system driver by overriding it per-volume or on the command line.

So it appears that the key is simply being ignored.
Comment by Kurt Marasco (celilo) - Wednesday, 28 October 2009, 00:28 GMT
A bit more info. A key also exists for "/system/storage/default_options/ntfs/mount_options" with a value of "umask=222".

So it is also possible that the "/system/storage/default_options/ntfs/fstype_override" is not being ignored (mounting using ntfs-3g), but that the permissions are being set based on the NTFS key instead of the NTFS-3G key.
Comment by Jan de Groot (JGC) - Wednesday, 28 October 2009, 07:36 GMT
That key belongs to gnome-mount, which is no longer used. The fix for this bug is to add a symlink for mount.ntfs to the ntfs-3g package.

Loading...