From owner-freebsd-virtualization@FreeBSD.ORG Tue Mar 16 16:49:12 2010 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDB11106568B for ; Tue, 16 Mar 2010 16:49:12 +0000 (UTC) (envelope-from miki@ceti.pl) Received: from relay.ceti.pl (relay.ceti.pl [62.121.128.10]) by mx1.freebsd.org (Postfix) with ESMTP id 970098FC2C for ; Tue, 16 Mar 2010 16:49:12 +0000 (UTC) Received: from tau.ceti.pl (tau.ceti.pl [62.121.128.11]) by relay.ceti.pl (Postfix) with ESMTP id E6223D52CC for ; Tue, 16 Mar 2010 17:22:44 +0100 (CET) Received: from [10.20.64.84] (unknown [89.174.237.33]) by tau.ceti.pl (Postfix) with ESMTP id AE512202FE4 for ; Tue, 16 Mar 2010 17:22:44 +0100 (CET) Message-ID: <4B9FB054.3030200@ceti.pl> Date: Tue, 16 Mar 2010 17:22:44 +0100 From: Mikolaj Rydzewski User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: ViirtualBox + cpio problems X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Mar 2010 16:49:12 -0000 Hello to everyone here, I'd like to share with you some strange problem I encountered recently. I wanted to test procedure for server upgrade. So I decided to perform such test using VirtualBox software. First I wanted to make some basic tests, I installed fresh 8.0-REL, everything seemed to work fine, up to the point I ran (with separate virtual drive mounted under /mnt): cd / find -x ./ | cpio -o | (cd /mnt; cpio -i) cpio threw error messages 'cannot create file', some files were restored correctly, some were corrupted. I performed similiar test several times, with errors every time. Has anybody got any clue what was wrong? Is it a known issue? Is there any configuration option to fix it? Thanks -- Mikolaj Rydzewski