[OpenAFS] bogus file dates

Neulinger, Nathan nneul@umr.edu
Fri, 7 May 2004 08:25:30 -0500


I have also seen this behavior from linux clients - but only when being
accessed through a translator like netatalk or samba. i.e. it's the
client's client that is screwing it up.

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-6679
UMR Information Technology             Fax: (573) 341-4216
=20

> -----Original Message-----
> From: openafs-info-admin@openafs.org=20
> [mailto:openafs-info-admin@openafs.org] On Behalf Of David Bear
> Sent: Thursday, May 06, 2004 11:22 PM
> To: Russ Allbery
> Cc: tracton@med.unc.edu; openafs-info@openafs.org
> Subject: Re: [OpenAFS] bogus file dates
>=20
> On Thu, May 06, 2004 at 04:58:10PM -0700, Russ Allbery wrote:
> > Gregg Tracton <tracton@med.unc.edu> writes:
> >=20
> > > We see files written into our afs space with bogus date=20
> timestamps,
> > > originating from windows, linux, and solaris clients. The=20
> timestamps
> > > display, depending on the client viewing the timestamp, as either
> > > December 31, 1969 or a day in 2033. It does not matter=20
> which of our 2
> > > afs file servers contains the volume. The problem is rare=20
> (once daily)
> > > and not reproducible.
> >=20
> > This was a bug in the AFS clients for at least Windows and I believe
> > Solaris some time back.  I remember we had this problem; I=20
> just don't
> > remember the exact versions that we had it with.  Upgrading=20
> to the current
> > versions of the AFS client should, in our experience, solve=20
> this problem.
>=20
> I recall seeing this will windows clients I think even using transarc
> afs... and probably open afs 1.2x. It was too long ago to remember,
> and rather rarely noticed.
>=20
> --=20
> David Bear
> phone: 	480-965-8257
> fax: 	480-965-9189
> College of Public Programs/ASU
> Wilson Hall 232
> Tempe, AZ 85287-0803
>  "Beware the IP portfolio, everyone will be suspect of trespassing"
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>=20
>=20