On Thu, 2023-11-30 at 07:01 -0600, Roger Heflin wrote:

That being said, I don't know that users and/or owner options *WORK* for network disks.   Those options likely do not also work as any disk that has actual owners info stored on them.  They are usually used with dos/fat/fat32 type fses tha do not have any user info on the disks/files.

That will depend on the disk's filing system. Various network storage devices are actually using Linux, with an ext filing system, so file permissions *can* be just the same on the NAS as your local storage.

* This depends on how they handle things. Traffic can be filtered, and everything loses individual ownership and gets assigned basic read and write permissions.

I have one NAS that wants to do that. Changes everything to owned by root or nobody, with world-wide read and write permissions, only trying to impose ownership restrictions through how you log in. It seems like their way of handling the conflicting mess of Windows/Mac/Linux usage on the same device.

For old-school NFS, you need to be the same user on the NAS as the local system. This isn't the user name, but your user ID number.

[tim@fluffy tv-series]$ ls -l porridge -rw-rw-r--. 1 tim tim 0 Jan 7 2016 porridge

[tim@fluffy tv-series]$ ls -n porridge -rw-rw-r--. 1 1000 1000 0 Jan 7 2016 porridge

You can see on these listings that I am user number 1000, and also the same for the group name and number.

It is possible for there to be username translation, so user tim on the NAS is user tim locally, even if the user numbers don't match. But that's an extra service that I've never bothered with researching deeply. I think it requires both sides to have the feature, and that's not always going to be the case. Whereas I can easily set up users with the desired user numbers.

Stephen's original info snippet: 192.168.1.12:/mnt/HD/HD_a2 is the same as one of my Western Digital (so-called) My Cloud NASs (it doesn't appear to have any features that are actually "cloud" services).

It does support NFS, though required some jiggery pokery to switch it on, and the option switch disappeared during some update. It does support Linux user names, ownership, and file permissions. But it would periodically change the ownership of a parent directory away from myself, such as after any reboot, and I'd have to ssh into the NAS and chown it back to me.

Inside it, there's different mounts for the "Public" filespace and individual users spaces. And, right now, mine's doing its annoying semi-regular "No such file or directory" when you try at access a sub- directory that it's listing, and clearly does exist. It was working yesterday. This device is such a pain! As far as I'm concerned it's a disastrously designed piece of rubbish. One of their older My Book Live NAS devices was much more stable.

Another of its quirks was refusing access if its time and date were wrong (such as after a power failure, and it had booted up before the rest of the network was available).

For what it's worth, I don't use entries in fstab for it. I gave up on that years ago, because Linux would throw a fit at boot-up or shut-down if the NAS wasn't available at the time. The NASs go to sleep when idle, and can take an age to wake up. Sometimes they don't.

I use autofs, any time I access /net/the-hostname-of-my-nas/ it connects to it, and automatically lets it go some time after last access. There are no special options set (by me) about the NFS protocols it uses.

On 1/12/23 23:09, Stephen Morris wrote:

On 1/12/23 22:54, Stephen Morris wrote:

...

On 30/11/23 22:42, Stephen Morris wrote:

...

I have a network drive being mounted from the following entry in /etc/fstab:

192.168.1.12:/mnt/HD/HD_a2                /mnt/nfs                nfs     users,nconnect=2,owner,rw,_netdev             0 0

This results in the following definition in /etc/mtab:

192.168.1.12:/mnt/HD/HD_a2 /mnt/nfs nfs rw,nosuid,nodev,noexec,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,nconnect=2,timeo=600,retran s=2,sec=sys,mountaddr=192.168.1.12,mountvers=3,mountport=57759,mountproto=udp,local_lock=none,addr=192.168.1.12 0 0

I can read from the mount point but I can't write to it. A    touch /mnt/nfs/filetest.txt fails with a read only volume error:

touch: cannot touch '/mnt/nfs/filetest.txt': Read-only file system

Can anyone guide me on what I am doing wrong, I am using F39, and I believe the fstab specification worked fine in F38 before I upgraded to F39.

This is an old nas device that only support nfsvers=3. I have resetup the device via its web interface to specify that "All Accounts" have read/write on the cifs share the nfs share is on, but I still get the write failure. I also have a cifs share define with myself and my wife having read/write access to the cifs share, and when I mount the share I user the username and password that has been defined on the server, which also happens to match my linux credentials, which mounts successfully, but it also it also gets "Access Denied" failures on write.

I'm at a loss to understand why the write access doesn't work under F39, as under F38 I uploaded 530 holiday photos from my digital camera to the nas device and also used Rawtherapee to write the 530 file format converted photos to that nas device as well.

regards, Steve

I stopped the nfs service on the nas and restarted it, and also rebooted the nas, and that resolved the nfs write issue and also resolved the cifs write issue as well (I hadn't considered this as a requirement as this is the first time I've ever had to do this since I bought the nas 4 or 5 years ago, although having said this occasional electricity blackouts may have alleviated the need for this).

What I need to work out now is why on the cifs mount from /etc/fstab the mount process is ignoring the "nosetuids" option.

regards, Steve

regards, Steve

...

...

regards, Steve

-- _______________________________________________ users mailing list --users@lists.fedoraproject.org To unsubscribe send an email tousers-leave@lists.fedoraproject.org Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue

-- _______________________________________________ users mailing list --users@lists.fedoraproject.org To unsubscribe send an email tousers-leave@lists.fedoraproject.org Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue

-- _______________________________________________ users mailing list --users@lists.fedoraproject.org To unsubscribe send an email tousers-leave@lists.fedoraproject.org Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue