Re: NFS Mount Point Write Failure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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


regards,
Steve

--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

Attachment: OpenPGP_0x594338B1DE179AB2.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux