From owner-freebsd-arm@FreeBSD.ORG Mon Nov 12 20:48:32 2012 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 64494D53 for ; Mon, 12 Nov 2012 20:48:32 +0000 (UTC) (envelope-from dave@jetcafe.org) Received: from nahkohe.jetcafe.org (nahkohe.jetcafe.org [205.147.26.32]) by mx1.freebsd.org (Postfix) with ESMTP id 3EB708FC16 for ; Mon, 12 Nov 2012 20:48:32 +0000 (UTC) X-Envelope-To: freebsd-arm@freebsd.org Received: from [205.147.26.5] (hokkshideh4.jetcafe.org [205.147.26.5]) by nahkohe.jetcafe.org (8.14.2/8.14.2) with ESMTP id qACKmS3C091867 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Nov 2012 12:48:28 -0800 (PST) Message-ID: <50A1609C.4010105@jetcafe.org> Date: Mon, 12 Nov 2012 12:48:28 -0800 From: Dave Hayes User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120612 Thunderbird/13.0 MIME-Version: 1.0 To: Ian Lepore Subject: Re: Dreamplug and eSATA problems References: <50A150C7.2080805@jetcafe.org> <1352751189.1217.50.camel@revolution.hippie.lan> In-Reply-To: <1352751189.1217.50.camel@revolution.hippie.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2012 20:48:32 -0000 On 11/12/12 12:13, Ian Lepore wrote: > It suddenly occurs to me that I was reading/writing the raw > unpartitioned device. I wonder if the problem for some reason only > shows up when you do filesystem access? It might be interesting for you > to try a basic IO test such as > > dd if=/dev/zero of=/some_file bs=1m count=10 > > then > > dd if=/some_file bs=1m | hd -C > > and you should see output from hd that summarizes that everything was > the same as the first line (zeroes), or if there are glitches they'll > show as additional lines of output from hd. I tried basic file copy tests and they worked. Simple things like: cp bigfile bigfile2 sha256 bigfile bigfile2 My theory is that said corruption only happens when you try to use the network interface and the eSATA at once. I used both fetch and ftp in my tests just to be sure. Any file transfer I did from the network to the eSATA device causes this corruption. -- Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org >>>> *The opinions expressed above are entirely my own* <<<< A free society is one where it is safe to be unpopular. -- Adlai Stevenson