On 2018-04-08 17:21, Marc Chamberlin wrote:
On 04/08/2018 03:10 AM, Carlos E. R. wrote:
That's not the full fstab line. It would be better if you posted the actual output of the "mount" command, the line pertaining to this mount point.
Hi Carlos - OK here is what the "mount" command shows. It actually shows the mount point twice because I do a bind mount of the root "/" to "/slash" -
mount | grep quantum /srv/autofs/auto.quantum.Win10 on /mnt/samba/Win10/quantum type autofs (rw,relatime,fd=37,pgrp=1452,timeout=5,minproto=5,maxproto=5,indirect) /srv/autofs/auto.quantum.Win10 on /slash/mnt/samba/Win10/quantum type autofs (rw,relatime,fd=37,pgrp=1452,timeout=5,minproto=5,maxproto=5,indirect)
(sorry these lines get broken up when doing a copy paste....)
You need an extension for Thunderbird, "Toggle Word Wrap" which allows you to write long lines. I was expecting to see like here (local mount): /dev/sda2 on /Windows/C type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096) See the user_id? What I don't see there is the remote mount of samba, how it is mounted from the remote machine. Your lines seem to be a local mount. Wait, I must be blind. Of course, you are not using the IPs, but the machine name auto.quantum.Win10. I see.
As I mentioned I don't mount these directly in fstab, but I use autofs instead. So I will give you full disclosure of the contents of the autofs configuration files so that you can fully understand how I am mounting the Windows file system. In the file /etc/auto.master the relevant line is -
/mnt/samba/Win10/quantum /srv/autofs/auto.quantum.Win10 --timeout=5 --ghost
That points to the actual mount configuration file (in a separate partition /srv so I can reuse it whenever I upgrade openSuSE) and the contents of /srv/autofs/auto.quantum.Win10 is what I previously showed you -
# # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # Details may be found in the autofs(5) manpage c -fstype=cifs,rw,dir_mode=0777,file_mode=0777,credentials=/etc/smb1.auth,uid=1000,gid=100,vers=2.0 ://quantumWin10/C
Well, as you can see the file mode/dirmode and uid do not appear in the mount command line output. Try not specifying them?
But I can see from the above that maybe only user 1000 will have write access.
And no, you can not change permissions with chmod on an ntfs disk.
And I agree with you, it doesn't make sense to me that doing a chmod on an ntfs disk would affect anything. But that is exactly what happened and hence my inquiry. I had tried everything I could think of on the Windows system (quantumWin10) directly, to open up C:/Users/marc/Documents to allow me to copy a file from my OpenSuSE laptop into that Documents directory, but nothing worked. What was even more surprising was that I could create a sub-directory - C:/Users/marc/Documents/tmp and was able to copy files there. I have been doing this as a workaround, hoping that someday this problem would get fixed in an update, but it never has. This problem goes way back and I have never bothered reporting it cause I can work around it, although it is a PITA. Anywise, I decided to try and tackle this problem again and this time I discovered that by changing the apparent permissions on my Linux laptop, on /mnt/samba/Win10/quantum/C/Users/marc/Documents from -r--r--r-- to -rw-r--r--, I was then able to copy files into the Documents folder from my OpenSuSE laptop! Totally surprised me because I did that on a whim without expecting it to work...
What this is saying to me is the Linux has a perspective of what the permissions are on mounted Windows NTFS file systems that is independent of actual permissions as understood by the Windows system. And that this *perceived* perspective must be changed also since it affects one's ability to access mounted Windows file systems. If I am right, then IMHO this is an extremely bad model, since it is totally confusing and NOT intuitively obvious on how to set permissions so as to make a mounted file system usable.
Mmm... :-? Maybe via samba you get different permission set than mounting locally a windows filesystem. This is something I haven't investigated.
From the responses I am getting here, my guess is that no one else has seen this, and yes for the most part accessing mounted file systems works for me as well. But this problem has showed up for my on all my Windows mounted file systems for the Documents folder so I don't know what to make of it. I can work around it, now that I know how, but it just seems very wrong that Linux is working with some sort of perceived permissions that are not related to the actual permissions of a Windows folder, and that I have to set the permissions on both systems in order to write to the Documents folder.
Thoughts? Marc....
Well, I don't have a windows machine permanently, so I don't have samba mounts to it. I can't try to replicate your setup. -- Cheers/Saludos Carlos E. R. (testing openSUSE Leap 15.0, at Minas-Anor) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org