Your initial topic didn’t mention NTFS and it should be irrelevant on Linux
According to the motherwiki you definately shouldn’t use uid and gid
Warning: Using
uid
and/orgid
as mount options may cause I/O errors, it is recommended to set/check correct File permissions and attributes instead.
– Samba - ArchWiki
Permissions on the content is irrelevant when it comes to NTFS - what is relevant though is your mountpoint - which must have the the correct permissions set e.g.
chmod ugo+rw /loc
Sharing partitions is not an issue - when they have been mounted no matter where they are mounted - my personal preference is either /a on a workstation and /data on a server with additional bind mount into /srv for system protection.
I have been a sysadmin for a living and when creating shared resources always use a dedicated structure - there is nothing that beats predicatability when it comes to troubleshooting.
One of your partitions
It would be better to use a more permanent idenfication and label the partition, also remove the fluff added by Gnome Disks or your troubleshooting steps
e2label /dev/sdb1 Lothlorien
Then mount without the fluff and uid gid stuff
UUID=A0E42A6AE42A4340 /loc/Lothlorien ntfs defaults 0 2
You may find [root tip] [How To] Samba Server From Scratch interesting - albeit no relation to Windows and NTFS.
When dealing with NTFS - the permissions on the mountpoint e.g. /loc will dictate what the samba service will allow.
Your mystery - moving the mountpoints inside your home is permission related - my guess is that you didn’t create a samba user.
Perhaps the combination of a missing samba user, your gid, uid in the mount options and the mount inside a tree with initial permissions of your gid and uid inadvertently solved your issue.
I think you have been labyrinting a xy problem where you would likely be better of starting from scratch.
I am the trial’n’error guy - so I have often forced myself to start over - attacking the issue from a different angle. This forum has been an invaluable tutor in that regard.
Remember
- a system user is not a samba user
- a samba user requires a system user