> No solution, but we see the same - apparently transarc
> afs had a problem and all volumes created in that period
> all have the epoch as their create time.
Well, that's not what we're seeing.
Any volume we create *today* on our OpenAFS servers has
the UNIX epoch as the create date.
Our entire cell is time-synched fine.
Performing the 'vos create' from an IBM AFS client or OpenAFS
client makes no difference.
bash-3.2$ vos create fs1 a fs1-a
Volume 2023883358 created on partition /vicepa of fs1
bash-3.2$ vos examine fs1-a
fs1-a 2023883358 RW 2 K On-line
fs1.mitre.org /vicepa
RWrite 2023883358 ROnly 0 Backup 0
MaxQuota 5000 K
Creation Wed Dec 31 19:00:00 1969
Last Update Wed Dec 31 19:00:00 1969
0 accesses in the past day (i.e., vnode references)
RWrite: 2023883358
number of sites -> 1
server fs1.mitre.org partition /vicepa RW Site
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
