Date: Mon, 12 Nov 2012 12:48:28 -0800 From: Dave Hayes <dave@jetcafe.org> To: Ian Lepore <freebsd@damnhippie.dyndns.org> Cc: freebsd-arm@freebsd.org Subject: Re: Dreamplug and eSATA problems Message-ID: <50A1609C.4010105@jetcafe.org> In-Reply-To: <1352751189.1217.50.camel@revolution.hippie.lan> References: <50A150C7.2080805@jetcafe.org> <1352751189.1217.50.camel@revolution.hippie.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50A1609C.4010105>