From owner-freebsd-current@FreeBSD.ORG  Wed May  2 17:42:43 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 9C6F116A400
	for <freebsd-current@freebsd.org>; Wed,  2 May 2007 17:42:43 +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 7448113C465
	for <freebsd-current@freebsd.org>; Wed,  2 May 2007 17:42:43 +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 <jclark@metricsystems.com>)
	id 1HjIqW-00068a-6G; Wed, 02 May 2007 13:42:32 -0400
Message-ID: <4638CE63.50209@metricsystems.com>
Date: Wed, 02 May 2007 10:46:11 -0700
From: John Clark <jclark@metricsystems.com>
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: Chuck Swiger <cswiger@mac.com>
References: <4638C84E.2000704@metricsystems.com> <4638C98F.3070607@mac.com>
In-Reply-To: <4638C98F.3070607@mac.com>
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: 
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2007 17:42:43 -0000

Chuck Swiger schrieb:
> 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?

What I'm doing is cloning a disk, and making it network accessible. So 
it is an 80 GB disk image.

When I mount the 'results', fsck, does start to pick up problems,  and 
on one of the partitions, basically resulted
in a slew of corrupted inodes.

So my suspicion is that there are missing blocks scattered throughout.

 >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'll see if I can set this up... but that would only verify that dd 
wasn't doing something strange...

One trick I tried was to use 'tee' to create the NFS image, and then 
continue the pipe with a 'cksum':

dd if=/dev/ad0 |  tee Disk.img | cksum

Tee stopped at some point, probably about 2.5 GB with a 'file too 
large'... the CVS sources that I'm using
are pretty recent, as in within the last month...