This issue is still present, as it should :
[root@dimension ntfslowprof]# ntfs-3g -o uid=0,gid=500 ../images/cf32M-9.clone
disk
[root@dimension ntfslowprof]# exit
exit
[linux@dimension ntfslowprof]$ cd disk/linux
[linux@dimension linux]$ bunzip2 linemode.try.bz2
bunzip2: I/O or other error, bailing out. Possible reason follows.
bunzip2: Operation not permitted
Input file = linemode.try.bz2, output file = linemode.try
bunzip2: Deleting output file linemode.try, if it exists.
[...]
[linux@dimension linux]$ strace bunzip2 linemode.try.bz2
[...]
fchmod(4, 0100777) = -1 EPERM (Operation not permitted)
write(2, "\nbunzip2: I/O or other error, ba"..., 69
bunzip2: I/O or other error, bailing out. Possible reason follows.
) = 69
Explanation : when mounting with uid=0,gid=500 the files are created as
owner root, and a user process cannot do a chmod on a file it does not
own. With these mount parameters the check is done by the kernel and the
chmod does not even reach ntfs-3g (so a "silent" optionhas no effect).
When mounting this way, you should get "Warning : using problematic
uid==0 and gid!=0" in your syslog file. You also can only set the mtime
to the current time, and copying a file does not preserve the mtime.
In real life, I do not have this issue, because I mount with option
"permissions".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/146225
Title:
bunzip2 cannot extract files
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/146225/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
