pkg/46339: afpd (netatalk-2.2.1nb3) on NetBSD-5/sparc64 shows future timestamps on client

[sieker%causalis.com@localhost]

>Number:         46339
>Category:       pkg
>Synopsis:       afpd (netatalk-2.2.1nb3) on NetBSD-5/sparc64 shows future 
>timestamps on client
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Apr 16 08:20:01 +0000 2012
>Originator:     Bernd Sieker
>Release:        NetBSD 5.0_STABLE
>Organization:
Causalis Limited
>Environment:
System: NetBSD sauerstoff.home.loc 5.0_STABLE NetBSD 5.0_STABLE (SAUERSTOFF) 
#3: Thu Feb 11 12:00:20 CET 2010 
bernd%sauerstoff.home.loc@localhost:/usr/source/5.x/src/sys/arch/sparc64/compile/SAUERSTOFF
 sparc64
Architecture: sparc64
Machine: sparc64

>Description:
An afpd server is running on NetBSD 5.0_STABLE on a Sun Netra T1 105 (sparc64, 
64bit), client is a Mac Mini with Intel Core i5 CPU running Mac OS X 10.7.3.

Files and directories are shown with a silly timestatmp on the client, about 
4490 days into the future. All dates appear to be correct on the server 
filesystem, even for files newly created from the client, they are only shown 
wrong to the client.

netatalk pkg version is 2.2.1nb3 built natively from pkgsrc-2012Q1 without any 
additional compiler options.

cnid-scheme is dbd, but other options produce the same result.

There is only one client machine using the server.

Earlier versions of netatalk/afpd worked fine when the server was NetBSD-3/i386.

>How-To-Repeat:
Build and run netatalk/afpd on sparc64, connect from a Mac using Mac OS X 
10.7.3, compare timestamps as viewed on the client as opposed to actual dates 
on the server filesystem.

>Fix:
Workaround: use samba to export filesystems to the Mac. It works, but requires 
TCP parameter tuning on the Mac to achieve even acceptable speed, which is 
still slower than using afp.