Date: Sun, 13 Apr 1997 00:18:31 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: m.sapsed@bangor.ac.uk (M.Sapsed) Cc: freebsd-questions@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Re: 2.2.1/amd problems Message-ID: <19970413001831.XL04295@uriah.heep.sax.de> In-Reply-To: <Pine.LNX.3.96.970410132832.8557I-100000@demo1.bangor.ac.uk>; from M.Sapsed on Apr 10, 1997 13:30:43 %2B0100 References: <Pine.LNX.3.96.970410132832.8557I-100000@demo1.bangor.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
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 joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970413001831.XL04295>