From owner-freebsd-current@FreeBSD.ORG  Thu May  3 20:59:58 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 8B41616A400
	for <freebsd-current@freebsd.org>; Thu,  3 May 2007 20:59:58 +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 6319213C48C
	for <freebsd-current@freebsd.org>; Thu,  3 May 2007 20:59:58 +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 1HjiOy-0001FR-BE
	for freebsd-current@freebsd.org; Thu, 03 May 2007 16:59:48 -0400
Message-ID: <463A4E2F.9050204@metricsystems.com>
Date: Thu, 03 May 2007 14:03:43 -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: freebsd-current@freebsd.org
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
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: Re: NFS problem -- solved.
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: Thu, 03 May 2007 20:59:58 -0000

John Clark schrieb:
> 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 looked in to this, and what is happing, is this.

I'm booting a FreeBSD diskless node, to 'clone' the existing harddrive. 
The FreeBSD boot code
apparently mounts the root file system usin NFS V2, which has the 2.5 GB 
(or so) file
size limit, due to using only a signed 32 bit integer for file size. 
This was found in the 'pxe' boot
code.

By executing an explicit 'mount' command with the '-3' option, I 
selected NFS V3, which
does not have this limitation, and was able to copy a previously 
captured 80 GB image onto
the harddrive. I'll check the other way around after I do an fsck on the 
resulting cloned drive.

John Clark.