From owner-freebsd-usb@FreeBSD.ORG Mon Jun 25 22:30:53 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D7B70106566B for ; Mon, 25 Jun 2012 22:30:53 +0000 (UTC) (envelope-from muxx.mailinglists@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 598F18FC0C for ; Mon, 25 Jun 2012 22:30:53 +0000 (UTC) Received: by lbon10 with SMTP id n10so8735775lbo.13 for ; Mon, 25 Jun 2012 15:30:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=m+THOoXy4XpjbJXt+GtzrJJGcM+BI+H6oP/2sZQVDDs=; b=B8CNc6fUb7YKyt8wQGgV7g2nTe/5dUitqlSIAMZKDRlkm0VNVntO09xDmRHj8HNuIW MxnmE8hGPIYFf3SqOel2g8BRW/x4v2UK3Dn4mpyZnX24bSV0wHWJyg9buiTuy3TZnlpk HEr1I41peylDuY+h7iIpffrsx4UGm7FeOrfnY8D2WAkNinvMZCxvisUE8+xXJcKn6A7r bWXkFWBbpocPOBrqpq10Ax5iJuRQl3NVBhImvM98Mw7P3e+jf64jwPBVT3hf+wn9TRy+ LUgpIkedk/dLclK4G6LwUHKggrNVZpyXL7fzul7vT+pfMB3h3H9lLG0HOEMo0KT+HaT5 YMgQ== MIME-Version: 1.0 Received: by 10.152.112.138 with SMTP id iq10mr13801182lab.13.1340663452285; Mon, 25 Jun 2012 15:30:52 -0700 (PDT) Received: by 10.112.26.163 with HTTP; Mon, 25 Jun 2012 15:30:52 -0700 (PDT) In-Reply-To: <201206251700.39759.hselasky@c2i.net> References: <201206241533.08745.hselasky@c2i.net> <201206251700.39759.hselasky@c2i.net> Date: Mon, 25 Jun 2012 23:30:52 +0100 Message-ID: From: maxim naumov To: Hans Petter Selasky Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-usb@freebsd.org Subject: Re: Seagate FreeAgent GoFlex 1.5TB external HDD problems X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2012 22:30:54 -0000 On Mon, Jun 25, 2012 at 4:00 PM, Hans Petter Selasky wrote: > BTW: You could try to make a simple c-test program that reads and writes > random LBA's from user-space, and see when it stops working. left it running iozone -a on the block device for the whole evening. iozone does lots of reads and writes of different sizes ("record sizes of 4k to 16M for file sizes of 64k to 512M" from the man). observed transfer rates in iostat smaller and larger than with previous tests. no errors detected. 8( however, I don't think iozone will seek further than 512M. previously the errors appeared with higher LBAs. not sure if the failure depends on offset, time, temperature, whatever. will leave running iozone -A overnight. to be honest, I was expecting it to fail much sooner. I am quite puzzled why the fact of using a filesystem makes it fail. /max