zfs discuss - Dec 2008 - ZFS+NFS4 strange timestamps on file creation

Has anyone seen files created on a linux client with negative or zero
creation timestamps on zfs+nfs exported datasets?

Yes, I''ve seen them on nfs filesystems on solaris10 using a Netapp nfs
server.
Here''s a link to a solution that I just implemented on a solaris10
server:
https://equoria.net/index.php/Value_too_large_for_defined_data_type

On Thu, 2008-12-04 at 15:31, Scott Williamson wrote:
> Has anyone seen files created on a linux client with negative or zero
> creation timestamps on zfs+nfs exported datasets?
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
-- 
Ed Spencer                      http://home.cc.umanitoba.ca/~fastedy
UNIX System Administrator       Academic Computing and Networking
EMail: Ed_Spencer at UManitoba.CA  The University of Manitoba
Telephone: (204) 474-8311       Winnipeg, Manitoba, Canada R3T 2N2

On Thu, Dec 4, 2008 at 4:52 PM, Ed Spencer <Ed_Spencer at umanitoba.ca>
wrote:
> Yes, I''ve seen them on nfs filesystems on solaris10 using a Netapp
nfs
> server.
> Here''s a link to a solution that I just implemented on a solaris10
> server:
> https://equoria.net/index.php/Value_too_large_for_defined_data_type
I tried that and saw no change. I can ls the files on my linux client
and solaris 10 server without getting that error message "Value too
large for defined data type" both before setting that tune option and
after.

I am going to blame the application for now.