Date: Tue, 21 May 1996 12:13:15 -0400 (EDT) From: Andrew Gallatin <gallatin@stat.Duke.EDU> To: current@FreeBSD.org Subject: NFS v3 problem Message-ID: <199605211613.MAA18122@diego.isds.duke.edu>
next in thread | raw e-mail | index | archive | help
Understanding that I'm doing so at my own risk, I've been using the NFS v3 support in -current. And I've found a problem. I've been building some software from our departmental source archive. The filesystem is NFS mounted (from a Dec Alpha running Digital UNIX 3.2c) using the options -3,-l. Under this arrangement, I'm having a reproducible problem building a library that's a component of a stats package. When ar is run on an nfsv3 mounted fs I get the following problem: % ar cru libblas.a dasum.o daxpy.o dcopy.o ddot.o dmach.o dnrm2.o drot.o drotg.o dscal.o dswap.o idamax.o % ranlib libblas.a ranlib: libblas.a: Invalid argument I think that I've tracked this down to ar interacting with nfsv3; it doesn't seem to matter if the f77 or ranlib steps are run when the fs is mounted nfsv2 or nfsv3. Ranlib will always fail if ar was run on an nfsv3 mounted fs, and always succeed if ar was run on an nfsv2 mounted fs. If there's anything further I can do to help track this down, I'll be happy to help out however I can. BTW, my system is a Micron pentium-pro 180, some sort of Orian chipset, 16MB RAM, 1G IDE, $20 ne2000-clone ISA ethernet card. Drew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605211613.MAA18122>