From owner-freebsd-fs@FreeBSD.ORG Fri Sep 26 10:41:53 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 18BA716A4B3 for ; Fri, 26 Sep 2003 10:41:53 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2338E44015 for ; Fri, 26 Sep 2003 10:41:52 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38lc0ri.dialup.mindspring.com ([209.86.3.114] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 1A2wbE-0006QV-00; Fri, 26 Sep 2003 10:41:49 -0700 Message-ID: <3F747A32.C407D40F@mindspring.com> Date: Fri, 26 Sep 2003 10:41:06 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Stefan Moro References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4942583874a9b23bedce081689d790e3e93caf27dac41a8fd350badd9bab72f9c350badd9bab72f9c cc: freebsd-fs@freebsd.org Subject: Re: mv & NFS problem.. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Sep 2003 17:41:53 -0000 Stefan Moro wrote: > Hello.. > I'm running FreeBSD 5.1 on a computer configured as an nfs-client and > freebsd4.8 on a computer configured as an nfs-server. When I try to move > something from the client to a partition on the server mounted on the > client in fstab using mv the client crashes. The server should be working > fine since there is no problem when using mv from a FreeBSD4.8 client to > the server. > > Using mv from the server to the client works fine.. What happens if you use "cp" or "dd" instead to copy the file from the client to the server? There are some very different code paths that get exercised by the 3, and it would be useful to know whether it's the explicit write path, the page fault write path, the explicit read path, the page fault read path, or some combination of the 4 that result in the error. Using the 'cp' and 'dd' approach, you would eliminate/implicate 3 of the code paths (given your existing results with 'mv'). -- Terry