Patrick_3000
Contributor
- Joined
- Apr 28, 2021
- Messages
- 167
I have Scale set up as my primary NAS, and on my top level dateset, I have myself (my user name) as the dataset owner, with full control including over child datasets, and my spouse with traverse privileges to the top level dataset, which is necessary because she has shared access to one of the child datasets.
In any case, I don't think the "traverse" privileges have anything to do with the problem I'm having.
Here is the problem I'm having: Whenever I access the Samba share to the top level dataset or any child datasets from a Windows client, permissions get messed up, and I'm no longer able to back up the dataset using rsync. In particular, copying or moving files into or out of the dataset on a Windows client causes this problem. When I access the datasets from a Linux client, there is no problem. It only happens when I access the datasets from a Windows client. (Note that whenever the problem occurs, I can always fix it by manually resetting the permissions for the dataset from the Scale web interface, but it's time-consuming to have to do this repeatedly.)
What's even more strange is that, when this problem occurs, viewing the datasets, including the offending files or folders, from a Linux client doesn't show any problem. It still shows my username as the owner, with full control.
Does anyone have any suggestions as to what could be causing this problem or how to diagnose it further? To some extent, it appears to be a Windows problem, but Windows doesn't play well with Linux/Unix permissions, so I'm not sure there is any way to fix the problem in Windows. Perhaps there is some workaround to fix it in Scale.
In any case, I don't think the "traverse" privileges have anything to do with the problem I'm having.
Here is the problem I'm having: Whenever I access the Samba share to the top level dataset or any child datasets from a Windows client, permissions get messed up, and I'm no longer able to back up the dataset using rsync. In particular, copying or moving files into or out of the dataset on a Windows client causes this problem. When I access the datasets from a Linux client, there is no problem. It only happens when I access the datasets from a Windows client. (Note that whenever the problem occurs, I can always fix it by manually resetting the permissions for the dataset from the Scale web interface, but it's time-consuming to have to do this repeatedly.)
What's even more strange is that, when this problem occurs, viewing the datasets, including the offending files or folders, from a Linux client doesn't show any problem. It still shows my username as the owner, with full control.
Does anyone have any suggestions as to what could be causing this problem or how to diagnose it further? To some extent, it appears to be a Windows problem, but Windows doesn't play well with Linux/Unix permissions, so I'm not sure there is any way to fix the problem in Windows. Perhaps there is some workaround to fix it in Scale.
