https://bugs.kde.org/show_bug.cgi?id=387936
--- Comment #6 from Tore Anderson <t...@fud.no> --- (In reply to Nate Graham from comment #5) > Thanks for the new info. Can you provide details about your method of > mounting it so we can try to figure out what combination of options triggers > this bug? Standard mounting from /etc/fstab: nas2-osl1:/volume1/homes/@LH-REDPILL-LINPRO.COM/0/tore-7097 /nfshome nfs defaults 0 0 The resulting /proc/mounts entry: nas2-osl1:/volume1/homes/@LH-REDPILL-LINPRO.COM/0/tore-7097 /nfshome nfs4 rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp6,timeo=600,retrans=2,sec=sys,clientaddr=2a02:c0:(snip),local_lock=none,addr=2a02:c0:(snip) 0 0 The mount is writable just fine from other applications, such as the shell: $ stat /nfshome File: /nfshome Size: 6654 Blocks: 0 IO Block: 32768 directory Device: 38h/56d Inode: 4727201 Links: 1 Access: (0755/drwxr-xr-x) Uid: ( 7097/ tore) Gid: ( 7097/ tore) Context: system_u:object_r:nfs_t:s0 Access: 2018-07-04 14:16:34.555886284 +0200 Modify: 2018-07-04 14:16:33.518885060 +0200 Change: 2018-07-04 14:16:33.518885060 +0200 Birth: - $ touch /nfshome/test $ rm /nfshome/test $ I believe the NFS server is a Synology RackStation RS3617xs. Tore -- You are receiving this mail because: You are watching all bug changes.
