From owner-freebsd-current@FreeBSD.ORG Wed May 2 17:16:35 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9640D16A400 for ; Wed, 2 May 2007 17:16:35 +0000 (UTC) (envelope-from jclark@metricsystems.com) Received: from server300.snhdns.com (server300.snhdns.com [204.15.192.210]) by mx1.freebsd.org (Postfix) with ESMTP id 6FCB313C447 for ; Wed, 2 May 2007 17:16:35 +0000 (UTC) (envelope-from jclark@metricsystems.com) Received: from ip67-89-211-170.z211-89-67.customer.algx.net ([67.89.211.170] helo=[192.168.0.94]) by server300.snhdns.com with esmtpa (Exim 4.63) (envelope-from ) id 1HjIRH-00040R-De for freebsd-current@freebsd.org; Wed, 02 May 2007 13:16:27 -0400 Message-ID: <4638C84E.2000704@metricsystems.com> Date: Wed, 02 May 2007 10:20:14 -0700 From: John Clark Organization: Metric Systems, Inc. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.8.1.2) Gecko/20070222 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server300.snhdns.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - metricsystems.com X-Source: X-Source-Args: X-Source-Dir: Subject: NFS problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 02 May 2007 17:16:35 -0000 I am copying a 'disk image' to an NFS mounted volume. I'm using: dd if=/dev/ad0 of=Disk.img After dd completes the number of blocks indicated is what the raw disk device should be. However, when I look at the NFS mounted image, the file size is anything but the 80 GB size it should be. I have not used NFS very much in the last few years, but I don't recall such data loss as being something to worry about. The NFS transactions, while using UDP, may be 'lost', but there was some form of retry and eventually the file data would be received, or ultimately the NFS client would emit some error message. Is there some option that I have not enabled in the kernel build, or well known problem that could be the reason for this behavior. Thanks, John Clark.