total 56
drwxr-xr-x 2 root root 4096 Apr 4 19:11 data
drwxrwxrwx 1 root root 12288 Mar 24 15:52 Data
drwxrwxrwx 1 root root 40960 Apr 5 21:34 Fun
I noticed something weird. The files and folders inside any of the main directory of 2 drives can be partially modified, but any subfolder canât be.
For example: /mnt/Fun/<file 1>or<folder 1> (This <file 1> or <folder 1> in the main directory can be copied, cut, renamed and deleted, but canât be tagged, duplicated or compressed).
But, /mnt/Fun/<folder 1>/<file 2>or<folder 2> (This <file 2> or <folder 2> inside the <folder 1> canât be modified, it can only be copied).
Do you mean adding iocharset=utf8 inside one mount file, then reload and add inside the another mount file of the second drive? And I add only to the mount files, not the auto mount?
I think this works, finally . I donât know what does umask=0000 make? And is it dangerous to files or anything?
I tried it with systemd method and then disabled those file and moved them to another folder to test it on fstab. And till now it works fine. Iâll deeply try it and if I found any wrong, Iâll post it. Thank you so much for help.
@soundofthunder Thank you so much for your patience and help, I really appreciate your efforts.
umask=0000 ensures everything is rwx for user,group,other - and no it is not dangereous ntfs device but it would be quite unsafe on a Linux filesystem - it corresponds to chmod 0777 <path-or-name> or chmod ugo+rwx <path-or-name>.
The default umask for filesystems on Manjaro is 0022 which translates to u=rwx,g=rx,o=rx
I have learned something as well - something I wouldnât have been able to otherwise - I donât use Windows - I donât have any disks with Windows generated NTFS filesystems - so you helped me learn as well - so thank you.
What I think I have learned is:
The ntfs3 kernel driver applies some kind of ACL and that ACL is not inherited from the mountpoint but is read from the filesystem inside the mountpoint.
drwxrwxrwx 1 root root 12288 Mar 24 15:52 Data
drwxrwxrwx 1 root root 40960 Apr 5 21:34 Fun
If I had such ntfs device I would look deeper into the file tree and look at folder and file permission below /mnt/Data and /mnt/Fun
The umask tells the ntfs3 driver to apply read,write,execute on everything that is available on the device.
The execute is necesary only for folders - otherwise you wouldnât be able to navigate the filesystem.
The other is are self explainatory.
It is possible to experiment with the umask - remember default is 0022
Get current value
I am trying to do that, I found something.
When I make the systemd method, the existing files and folder ownership is root, but still I can control them as far as I test them. And the new created folder or files are owned by me as a user. On fstab method, itâs all owned by me except for a file I was trying on it in the terminal with sudo command to cut it, may be this changed the permissions of the file.
May be because in fstab I use this line with uid=1000?
I actually donât care about the permissions. All I want to have control ob my data. I just ask to avoid any errors in the future.
Another question, if you donât mind. In the systemd method, we add a line of the time after which the inactive drive will be unmounted. When I press on the drive again, will it request a password to mount it? As it requested from me the sudo password.
And if I want o mimic the systemd files in fstab, will this line be efficient?
Any permissions you think youâre assigning to the NTFS volume (through fstab, for example) are only being applied to the mount point folders - not the NTFS volume itself - this is normal when using NTFS volumes.
This is purely for extra clarification.
Apart from that you seem to have everything working as expected now.
Thatâs good to see.
.
. I donât know what does umask=0000 make? And is it dangerous to files or anything?