From owner-freebsd-current@FreeBSD.ORG Thu Jul 17 02:55:05 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDB4537B401 for ; Thu, 17 Jul 2003 02:55:05 -0700 (PDT) Received: from sweeper.openet-telecom.com (mail.openet-telecom.com [62.17.151.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 250FD43FBD for ; Thu, 17 Jul 2003 02:55:04 -0700 (PDT) (envelope-from petere@openet-telecom.com) Received: from mail.openet-telecom.com (unverified) by sweeper.openet-telecom.com ; Thu, 17 Jul 2003 09:57:08 +0100 Received: from [10.0.1.152] (10.0.1.152) by mail.openet-telecom.com (NPlex 6.5.027) id 3E82B2460004C17E; Thu, 17 Jul 2003 09:53:14 +0100 From: Peter Edwards To: =?iso-8859-1?q?S=B3awek=20=AFak?= Date: Thu, 17 Jul 2003 09:54:28 +0100 User-Agent: KMail/1.5.2 References: <867k6iagj4.fsf@thirst.corponet.era.pl> <3F16337B.3004C77E@mindspring.com> In-Reply-To: <3F16337B.3004C77E@mindspring.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200307170954.28580.petere@openet-telecom.com> cc: freebsd-current@freebsd.org Subject: Re: NFS problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 09:55:06 -0000 Hi, > > All the files are 0-sized, dates are set back to the epoch and > > directories are seen as files. Exporting ufs2 filesystems works as > > expected. I've had problems like this exporting CDs via NFS to solaris. Sorry the details are murky, but if its the same problem, there's a work-around. Check the dmesg output: does it complain about an "RRIP field" from the cd9660 code? From the source, I think it was "RRIP without PX field?" The CDs in question were official Sun CDs with Solaris applications (which, of course, doesn't mean their properly compliant to a standard, just that it's likely others will run into the same problem) If this is the issue, then mounting it with NFS v2 actually fixed the problem for me: I assume the richer operations from v3 were tickling a problem not noticed with v2. -- Peter