From owner-freebsd-stable@freebsd.org  Wed Feb  1 14:31:58 2017
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57040CCBE69
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Wed,  1 Feb 2017 14:31:58 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 161EA8BE
 for <freebsd-stable@freebsd.org>; Wed,  1 Feb 2017 14:31:58 +0000 (UTC)
 (envelope-from slw@zxy.spb.ru)
Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1cYvwy-0006pL-2k; Wed, 01 Feb 2017 17:31:56 +0300
Date: Wed, 1 Feb 2017 17:31:56 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Jakub Lach <jakub_lach@mailplus.pl>
Cc: freebsd-stable@freebsd.org
Subject: Re: FreeBSD 11.0-STABLE #0 r310265 amd64 seems to be cpi-ing garbage
 to mounted FAT32 fs after 10-20 GB.
Message-ID: <20170201143156.GE79121@zxy.spb.ru>
References: <1483038391207-6154963.post@n6.nabble.com>
 <op.yuzc2cebkndu52@53556c9c.cm-6-6b.dynamic.ziggo.nl>
 <1485952687570-6164655.post@n6.nabble.com>
 <20170201125059.GB3018@kib.kiev.ua>
 <1485954165392-6164661.post@n6.nabble.com>
 <20170201131826.GD3018@kib.kiev.ua>
 <1485957121778-6164672.post@n6.nabble.com>
 <20170201141840.GD79121@zxy.spb.ru>
 <1485959118559-6164677.post@n6.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1485959118559-6164677.post@n6.nabble.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 14:31:58 -0000

On Wed, Feb 01, 2017 at 07:25:18AM -0700, Jakub Lach wrote:

> I would think so, if only I would not clone the disk/system via the same USB
> port mere weeks ago.
> Moreover, sysutils/f3 fully writes and validates (checksums) 30G+ memory
> cards via the same port without problems.

In my case controller don't always be broken, only from some time.
Data corruption over my USB depends on data access pattern.