Hi,
I encountered the same bug and found out that was caused by the
following two reasons.
(1) Since kernel 2.6.22, range checks of utimes() system call
got more strict by a patch involved with utimensat().
(2) Linux NFS client uses a Sun convention for "set to current
sever time" in which an invalid value useconds=1000000 is
passed to server. However, unfsd tries to use it as-is
for changing timestamp of requested files through the
utimes() system call.
Thus, the nfs-user-server (unfsd) gets to fail against the
kernel 2.6.22 and later.
I wrote a patch to fix it by adding the Sun convention support.
The patch is available at
<http://marc.info/?l=linux-nfs&m=118724649406144&w=2>
It's for the nfs-user-server_2.2beta47-23.
I have also sent it to the original author,
but the mail was returned by Host unknown.
It seems that no-one now maintains this software except for
the Debian package maintainer.
I would be grateful if someone who maintains nfs-user-server
could try to apply the patch.
Regards,
Ryusuke Konishi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
