From owner-freebsd-current Thu Jan 21 21:42:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21186 for freebsd-current-outgoing; Thu, 21 Jan 1999 21:42:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21172 for ; Thu, 21 Jan 1999 21:41:58 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id VAA15941; Thu, 21 Jan 1999 21:53:13 -0500 (EST) (envelope-from luoqi) Date: Thu, 21 Jan 1999 21:53:13 -0500 (EST) From: Luoqi Chen Message-Id: <199901220253.VAA15941@lor.watermarkgroup.com> To: dillon@apollo.backplane.com, luoqi@watermarkgroup.com Subject: Re: Trouble executing from NFS with latest 4.0-current Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :Execute anything from NFS would result in an "Input/output error", but if I do > :a hexdump of the executable first, the execution would be successful. If I > :reverse the order, i.e., execute first then hexdump, execution would fail and > :hexdump would hang at "pgtblk". No problem with FFS. > : > :-lq > > Hmmm. It's working fine for me between two FreeBSD boxes. Do a > cvs diff against your entire /usr/src/sys tree first to make > sure you are up to date on all the patches. > > If it's still broken, we need to identify whether it is NFSV2, V3, > and whether the problem is related to FreeBSD<->FreeBSD or FreeBSD > w/ some other platform. Also any mount options, such as read and > write buffer settings, etc... > > -Matt > > Matthew Dillon > > Sorry, it was an outdated nfs.ko, please disregard the report. I had some trouble with making world because of the libcrypt stuff and I'm still struggling to get everything installed right. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message