From owner-freebsd-current@FreeBSD.ORG Wed May 2 17:25:39 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 04E6B16A400 for ; Wed, 2 May 2007 17:25:39 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.freebsd.org (Postfix) with ESMTP id CD80613C45A for ; Wed, 2 May 2007 17:25:38 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 4D4525C99; Wed, 2 May 2007 13:25:38 -0400 (EDT) X-Virus-Scanned: amavisd-new at codefab.com Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qoOfo3JfhtLn; Wed, 2 May 2007 13:25:36 -0400 (EDT) Received: from [192.168.1.3] (pool-96-224-43-99.nycmny.east.verizon.net [96.224.43.99]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 96BE15C47; Wed, 2 May 2007 13:25:36 -0400 (EDT) Message-ID: <4638C98F.3070607@mac.com> Date: Wed, 02 May 2007 13:25:35 -0400 From: Chuck Swiger User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: John Clark References: <4638C84E.2000704@metricsystems.com> In-Reply-To: <4638C84E.2000704@metricsystems.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: 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:25:39 -0000 John Clark wrote: > 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. How big is it? Is the data complete/intact up to the point when it stopped? Can you create enough local space on a second drive (or do this by individial partitions instead) to create the image locally, and then copy the file at once via NFS? It'd be nice to see whether that worked OK. > 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. One would hope so, yes. Is it possible that doing an fsync or system-wide sync would help get the blocks written out...? Does using tar or dump/rmt work any better? -- -Chuck