On Tue, 2014-03-18 at 19:51 +0100, Martin (KDE) wrote:
> Am 18.03.2014 11:09, schrieb Patrick O'Callaghan:
> > On Tue, 2014-03-18 at 07:46 +0100, Martin (KDE) wrote:
>
> >
> > Understood, however the /etc/fstab entry on the client side is
> > "user,rw,comment=systemd.mount" and the full set of mount options as
> > shown by "mount" is:
> >
> > rw,nosuid,nodev,noexec,relatime,vers=3,rsize=32768,wsize=32768
> > namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,
> > mountaddr=xxx.xxx.xxx.xxx,mountvers=3,mountport=901
> > mountproto=udp,local_lock=none,addr=xxx.xxx.xxx.xxx,user
> >
> > which I interpret to mean no async, though maybe I'm mistaken. The
> > server side is exporting async but AFAIK that isn't important here.
>
> I read a little bit further in the nfs man page. By default a nfs mount
> uses async mode, but file data is synced by special commands (i.e.
> fsync...). The application can set individual sync option as well. So it
> depends on three parts:
>
> - NFS Server settings
> - NFS Client settings
> - Application flags used on opening a file
Yes, I read that too. However the implication is that async is the
default when the mount options include "defaults", which in my case they
don't. It appears that in fact async is the default unless you
explicitly specify sync, i.e. the nfs manual is misleading.
I remounted using explicit sync and sure enough the problem goes away. I
suppose the only way to achieve the desired effect using async would be
for the client side to do some kind of polling, but even then I'm not
sure it would work.
Perhaps when copying to an async server the pop-up should show a warning
("Destination server is mounted asynchronously") instead of a spurious
transfer rate.
poc
_______________________________________________
kde mailing list
kde@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/kde
New to KDE4? - get help from http://userbase.kde.org
