Date: Fri, 18 Apr 1997 14:39:34 +0100 (BST) From: Doug Rabson <dfr@nlsystems.com> To: Martin Sapsed <m.sapsed@bangor.ac.uk> Cc: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>, freebsd-questions@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: 2.2.1/amd problems Message-ID: <Pine.BSF.3.95q.970418143534.428A-100000@herring.nlsystems.com> In-Reply-To: <Pine.WNT.3.96.970418095403.-194853A-100000@martin.bangor.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 18 Apr 1997, Martin Sapsed wrote: > On Sun, 13 Apr 1997, J Wunsch 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). > > I heard from Mike after my newsgroup post. My machine has a 16-bit WD > ethercard. > > I have since found that if I explicitly "mount server:/path /mnt" there > are no problems getting directory listings. Does this imply something to > do with the NFSV3 support in 2.2.x ? mount -3 blah gets an error. This > all worked fine in 2.1.7. > > The server in question runs SunOS 4.1.2 and the top of the amd map is > like this: I don't think it has to do with NFSv3. Other people are seeing this effect. I can reproduce it occaisonally but not reliably; I am working on trying to fix it though. The version of AMD in 2.2.x doesn't understand NFSv3. I only just updated the one in 3.0 for v3. Since SunOS 4.1.2 doesn't support v3, your mount -3 will fail. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95q.970418143534.428A-100000>