Subject: Another recent NFS problem
To: None <current-users@netbsd.org>
From: Mark Davies <mark@mcs.vuw.ac.nz>
List: current-users
Date: 07/08/2004 01:26:50
Since updating an NFS server from 1.6ZH to 2.0F I've started seeing the=20
following problem:

=46rom Solaris 9 NFS clients, accessing some files now fail with the error:=
=20
"Value too large for defined data type"  while those same files can be=20
accessed successfully from NetBSD and Tru64 clients.

eg.

sun%  ls -l ~/.kde/share/kde/config/kdeglobals
/u/staff/mark/.kde/share/kde/config/kdeglobals: Value too large for defined=
=20
data type

netbsd%  ls -l ~/.kde/share/kde/config/kdeglobals
=2Drw-------  1 mark  staff  11903 Jul  7 18:17
     /u/staff/mark/.kde/share/kde/config/kdeglobals

stat (on NetBSD) gives:

% stat ~/.kde/share/kde/config/kdeglobals
2818 399126 -rw------- 1 mark staff 1606952 11903 "Aug  5 09:15:44 1950"
 "Jul  7 18:17:32 2004" "Jul  7 18:17:32 2004" "Jan  1 12:00:00 1970"=20
32768 24 0 /u/staff/mark/.kde/share/kde/config/kdeglobals

% stat -r ~/.kde/share/kde/config/kdeglobals
2818 399126 0100600 1 1002 24 1606952 11903 -612499456 1089181052=20
1089181052 0 32768 24 0 /u/staff/mark/.kde/share/kde/config/kdeglobals


Having just done that I see the rather bogus looking access time.  So is th=
ere=20
some patch since around 22/6 that should fix this or can someone tell me=20
whats going on?

cheers
mark