Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 13 Apr 1997 16:08:24 -0400 (EDT)
From:      Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
To:        ponds!freefall.cdrom.com!freebsd-hackers
Subject:   Re: 2.2.1/amd problems
Message-ID:  <199704132008.QAA22110@lakes.water.net>

next in thread | raw e-mail | index | archive | help
As J"org wrote:
> 
> 
> As M.Sapsed wrote:
> 
> > >  More of a problem is that my automounted (via
> > > amd) home directory fails to appear when doing an ls or anything else,
> > > although it is mounted and ls of small subdirectories works fine. The
> > > home directory has 221 entries and another subdirectory which fails has
> > > 162 (I know they're large but they should work!) If I ask for ls on
> > > these dirs, it just sits there for about 30 mins until a message
> > > 
> > > /kernel: nfs server server:/path/path: not responding
> > > 
> > > appears. If you then do ctrl-C you get a prompt back and can get an
> > > instant listing of the smaller directories.
> 
> Mike Murphy reported me a similar problem (there's even PR # bin/1872
> open for it), where he finally found that the problem was the slow
> 8-bit ethernet card of his server.  Setting NFS readdir size down to
> 1024 might help, but amd doesn't offer this option.  Frankly, amd's
> option handling in this respect just sucks, there are more options to
> mount_nfs(8) now that are not supported by amd (like the NFSv3 stuff).
> 
> -- 
> cheers, J"org

 Yes! Yes!

 This is exactly my problem with NFS in 2.2.1 - I don't believe
amd has anything to do with it.

 Also, I've set the readdir size to 1024 (since I'm not doing amd, but
a direct mount) and the problem remains.

 See my other mail on 2.2.1 NFS problems in the -hackers list.

	- Dave Rivers -




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704132008.QAA22110>