Creation/modification time wrong on nfs disk

[Wim Van den Wyngaert · Accepted solution]

Dismounted and mounted (the NFS disk) again. The problem is solved. Can you test that too ?

Wim

[Hans Adriaanse]

Oke, I will try it, but not now. The other users will not like that :-).
Hope to find an occasion soon.
Thanx.

[Wim Van den Wyngaert]

http://www5.itrc.hp.com/service/patch/patchDetail.do?BC=patch.breadcrumb.main|patch.breadcrumb.search|&patchid=DEC-AXPVMS-TCPIP_ECO-V0503-184-4&context=openvms:alpha:7.3

RCP/PRESERVE (aka RCP -p) didn't preserve correct modification timestamp for files created in the summertime (daylight savings
in effect) but copied in the wintertime (standard time), or vice-versa. The timestamp is off by an hour (the daylight savings differential). Problem occurred for files copied to a VMS host, but not for files copied to non-VMS host.

May be this kind of bug is present in NFS ?

Wim

[Wim Van den Wyngaert]

A 6.2 client is persistently wrong, even after a reboot.

Wim

[Hans Adriaanse]

Yes !! A dismount an mount again from the nfs disk fixed the problem. Strange. Thank you all.

[Wim Van den Wyngaert]

But will it stay away ?

I had several systems with the problem. I'll continue to search and report when I find the WHY.

Wim

[Volker Halle]

Hans, Wim,

as far as I remember, you have to re-mount the NFS disk from the client after any changes to the system timezone...

You'll have a chance to verify and test this in 3 weeks ;-)

Volker.

[Wim Van den Wyngaert]

Volker,

No timezone changes.

But I checked all system to see if there is a relation with "time has changed since mount". And this seems to be the case. All 7.3 systems that mounted the disk before the time change have the problem. For the (10) 6.2 systems it is not the case. They are ALWAYS wrong.

Wim