Re: nfs - date & time (settingdelay?) -

Am 27.08.26 um 11:12 schrieb Simon Becherer via openSUSE Users:

 > ..... snip ....

have done more tests, to find more close the problem:

in addition to the slowdown i recognized at the moment:

the delay has to do with the copy of the files before:

here i am working inside "mc":

i copy from real computer nfs in network from one directory
of the above mentioned host to another directory of the host
a file. - now i open this file with the software from qemuclient.
i have the delay. after the file is opend, i see the date + time
when i do a "ll"  (or in mc) has changed to the actual time !!!

NOW i copy the original file over the date changed file like
i first copy it into the directory (without the file). - date time now is again old.
now i open this file again with the qemuclientsoftware. the date
time is not changed AND i do not have a delay!
(i could repeat this effect 100times...)

next test, i do copy the file as above, but now with the host computer,
the copy will not go over the nfs-connected computer.
i do not have a delay and i do not have the change of the date/time.

===== comming closer to the problem: ==============
third test, i copy like in the beginning (withe the nfs-connected computer),
i check date and time on the nfs connected computer, its old.
BUT when i check it at the host computer here it has the actual date and time.
so the copy OVER nfs changed date and time, but did not show this if connected
over nfs -. after about 3 minutes i can see the NEW date and time also over
nfs. and after this time i did not have any delay in opening the file.

next test:
using host computer (it has nfs client and server) over his own nfs
link to copy the file, date and time are not changed, no delay.

using another computer nfs copy, and date and time changed when i check
on host, changes after some minutes when i take a look over nfs

this was all copy with midnight commander and checking date an time with mc.

NOW i copy with "cp -p ...." date and time changed, as above when copy over network.
only difference is, i see the changed date and time immediately - the delay when
trying to open inside guest is the same.

BUT:

after 2-3 minutes (doing nothing) the original (correct) file date and time is restored and no delay.

because all of my systems have nfs host and client i checked from other computers
to others, all same effect, here all tumbleweed 20260815

ok, now i see that the date and time seems to change twice (mc copy) looking
into it direct on the system:
over network with mc-copy it shows after copy still original: 2010-06-21 17:55:38.000000000 +0200
direct after copy direct on the system: 2026-08-27 15:13:46.543905878 +0200
and after about 2 minutens              2026-08-27 15:14:51.175498604 +0200

and same with cp -p over network:

with ls -s --full-time:
direct after copy over network i see: 2010-06-21 17:55:38.000000000 +0200
direct after copy shown from local:   2026-08-27 15:20:26.770477842 +0200
some minutes later shown both:        2010-06-21 17:55:38.000000000 +0200

what is going on here ???????

i guess there is a bug in setting the date and time over nfs ?

what should i do? is this known? could anybody confirm?


simoN

-- 
www.becherer.de

-----BEGIN PGP SIGNATURE-----

wr0EABYIAG8FgmqQOyIJEDCnmz4w7QASRxQAAAAAAB4AIHNhbHRAbm90YXRpb25z
LnNlcXVvaWEtcGdwLm9yZ8GcP4XPMlvxJXka7xfua4BV9KXQk08QnfqHj/9mlSHs
FiEEqNbyKdqyczJbPSUyMKebPjDtABIAAG/iAQC0r/c1e+cDz7gWP0qpLEKXM6WM
VPbhIjw5wjwcbMQ+lAD+K3m61SSUVzwgJZQ7Fy5rg0O35D4JlyWQMUKghszIEQk=
=oeLs
-----END PGP SIGNATURE-----