Hi,

[ I'm mailing this to current-users because this is the system I'm using
  as the client now and maybe you know what is happening... ]

I have a i386 3.0_STABLE machine serving three directories:

/home/jmmv -maproot nobody:nogroup -network 192.168.1 -mask 255.255.255.0
/home/shared -maproot nobody:nogroup -network 192.168.1 -mask 255.255.255.0
/home/mldonkey/incoming -maproot nobody:nogroup -network 192.168.1 -mask 255.255.255.0

I mount these in a i386 3.99.23 machine using NFS TCP.  The following is
what I have in fstab:

max.home.network:/home/mldonkey/incoming /media/incoming nfs rw,-T
max.home.network:/home/jmmv /media/jmmv nfs rw,-T
max.home.network:/home/shared /media/shared nfs ro,-T

And this has been causing an annoying problem for a very long time already.
I don't know whose fault it is, if the server or the client.  The problem
is the following: I first boot the client and it mounts the shares
immediately, without any problem.  If I then reboot the client, the first
attempt to mount one of the file systems fails; waiting some time makes it
work though.  I get this:

Jul 29 13:33:04 dawn /netbsd: nfs server max.home.network:/home/mldonkey/incoming: not responding
Jul 29 13:34:19 dawn /netbsd: nfs server max.home.network:/home/mldonkey/incoming: is alive again

Although it seems to happen after a reboot (the share is unmounted and
mounted again too quickly, from server's point of view?), I'm afraid it's
somewhat random too: sometimes the problem does not appear.

I think I also saw this using Ubuntu as the client, as the system once came
up without any of the shares mounted.

Is it there something wrong in my setup?  Is this a bug and worth a PR?

Thanks.

-- 
Julio M. Merino Vidal <jmmv@NetBSD.org>