I have one of those 2.5" external drive that I store my mp3/flac in and it is formatted NTFS (in case I need to use someone else's Windows machine and it's 250GB, so no FAT) and mounted with write permission using ntfs-3g.

I was trying to edit the id3 tag on one of the file (with Ex Falso) and it gives an error "fail to write to file...". Yet it writes the tag successfully anyway. So this is not exactly a show stoper but very annoying because the error dialog would stop the tagger from tagging the rest of the files if I am doing a massive tag change.

I check the log files and did not discover any error posted by ntfs-3g. For reference, here's the mount options:

From command line, this is the problem:



but again, the tag is set anyway

Hi,


Which version ? (type ntfs-3g --help)


What are the permissions on the parent directory ? (type ls -ld .)

Regards

Jean-Pierre

files are mounted rw-rw-r--, directory are mounted rwxrwxr--
user=root, group=ntfsusers, and the I am doing this as member of ntfsusers group (same result as root).

sorry for the quick re-reply.

Hi,


This version has no support for permissions changing. When wanting to use an application which tries to change them and checks it does, you need the advanced version : http://pagesperso-orange.fr/b.andre/adv ... fs-3g.html

Regards

Jean-Pierre

Thanks for the answer. Like I said, it's no show stopper. So I'll wait for this feature to be made to the stable tree.

Awesome project. Thanks.

Hi,

The permission error message is correct. The access rights are enforced by the kernel, not NTFS-3G because you use the default_permissions mount option.

I don't know how you ended to this setup because default_permissions is an NTFS-3G internal, FUSE option what NTFS-3G turns on when one of the permission handling related mount options is used. This is documented in the NTFS-3G manual:


However I can't see you would use any such option and it looks like you added default_permissions manually what you mustn't do because you end up in an unsupported, inconsistent scenarios like this one.

So, please remove it and use the uid, gid, etc options. Then you will be able to modify the file without permission conflict, supposed the modifying user is indeed the one specified by the uid/gid options and have the right file permission.

Regards, Szaka

I am not sure if I am using it by accident. Here's my fstab line:


For convenience, I usually don't type "mount" on terminal, but when I plug in the usb drive, KDE4 would detect it and I just click the icon to mount. So, I could be KDE4's own mounting software is adding that option?

Ok, then it's not by accident.

Please follow the below

1. run 'strace -f -o id3.txt -p PID' where PID is the process id of 'Ex Falso'
2. reproduce the problem
3. exit strace (CTRL-C)
4. bzip2 id4.txt
5. send the compressed file to szaka@ntfs-3g.org or make it somewhere publicly available.

Thanks, Szaka

This seems to be the reasons: http://www.ntfs-3g.org/support.html#compressed

Workaround: copy the relevant file to a different name (DO NOT RENAME!) then you should be able to modify the copy.

Actually now I should ask something I have wondered for a while. When I first formatted the drive I made it compressed. After a while I realized that it's kind of studpid. When I go to "volume property" in Windows, I see a checkbox for compression. I am not sure if I can just uncheck it and apply or I have to reformat the drive.

You could also send a patch for compression write support ;-) But at the moment you should reformat.