tuxera / ntfs-3g

NTFS-3G Safe Read/Write NTFS Driver
https://www.tuxera.com/company/open-source
GNU General Public License v2.0
999 stars 149 forks source link

ntfs-3g ignored options uid and gid #97

Open SFR-lhsm opened 10 months ago

SFR-lhsm commented 10 months ago

Hello,

I'm using ntfs-3g (2022.10.3) on a Red Hat 9 server (5.14.0-362.13.1.el9_3.x86_64).

When I use one of the following commands mount -t ntfs-3g -o uid=2262 /dev/sde2 /mnt/shared_vmdk/datalan.vmdk mount -t ntfs-3g -o gid=1101 /dev/sde2 /mnt/shared_vmdk/datalan.vmdk

It seems that uid=2262 or gid=1101 are ignored (user_id,group_id have the value 0) mount | grep sde2 _/dev/sde2 on /mnt/shared_vmdk/datalan.vmdk type fuseblk (rw,relatime,user_id=0,group_id=0,default_permissions,allowother,blksize=4096)

It was working well on a ntfs-3g (2017.3.23) on a Red Hat 6 server (2.6.32-754.35.1.el6.x86_64).

Thanks in advance for your help.

More information on configuration :

- uname -s -r

Linux 5.14.0-362.13.1.el9_3.x86_64

- ntfs-3g -v

ntfs-3g 2022.10.3 integrated FUSE 28 - Third Generation NTFS Driver Configuration type 7, XATTRS are on, POSIX ACLS are on

jpandre commented 10 months ago

/dev/sde2 on /mnt/shared_vmdk/datalan.vmdk type fuseblk (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)

The user_id and group_id appear as zero because uid and gid options are processed at ntfs-3g level. You need to check how the owership of a file looks like, and if you do not define the user mapping, the ownership is not recorded to the device.