The user used to connect on the network drive has to have write capability. Log in as that user and try to write at the directory of the mount point.
On Thu, Nov 30, 2023 at 8:02 AM Roger Heflin <rogerheflin@xxxxxxxxx> wrote:
you specified "nfs" as the mount. And that should mount nfs4 with
tcp, but mounted with nfs and udp so whatever is on the other end is
old and/or has tcp/nfsv4 disabled.
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.
Retest as root and see if that changes anything. LIkely you need to
be root (if the other end allows root) or you need to be the same UID
as what owns the directories/files, or you need to setup one of the
nfs-uid-mapping programs (I know they exist, I don't use them).
On Thu, Nov 30, 2023 at 5:42 AM Stephen Morris <samorris@xxxxxxxxxxxxxxx> 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.
>
> 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
--
_______________________________________________
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
--
------------------------------
/\_/\
|O O| pepebuho@xxxxxxxxx
~~~~ Javier Perez
~~~~ While the night runs
~~~~ toward the day...
m m Pepebuho watches
from his high perch.
/\_/\
|O O| pepebuho@xxxxxxxxx
~~~~ Javier Perez
~~~~ While the night runs
~~~~ toward the day...
m m Pepebuho watches
from his high perch.
-- _______________________________________________ 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
