From owner-freebsd-current Thu Jan 21 18:04:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08715 for freebsd-current-outgoing; Thu, 21 Jan 1999 18:04:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08705 for ; Thu, 21 Jan 1999 18:04:56 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id SAA46934; Thu, 21 Jan 1999 18:04:45 -0800 (PST) (envelope-from dillon) Date: Thu, 21 Jan 1999 18:04:45 -0800 (PST) From: Matthew Dillon Message-Id: <199901220204.SAA46934@apollo.backplane.com> To: Luoqi Chen Cc: current@FreeBSD.ORG Subject: Re: Trouble executing from NFS with latest 4.0-current References: <199901220059.TAA15433@lor.watermarkgroup.com> 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message