From owner-freebsd-stable@freebsd.org  Wed Feb  1 14:16:31 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 00849CCB7EA
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Wed,  1 Feb 2017 14:16:31 +0000 (UTC)
 (envelope-from jakub_lach@mailplus.pl)
Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15])
 by mx1.freebsd.org (Postfix) with ESMTP id E282F186F
 for <freebsd-stable@freebsd.org>; Wed,  1 Feb 2017 14:16:29 +0000 (UTC)
 (envelope-from jakub_lach@mailplus.pl)
Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37])
 by mbob.nabble.com (Postfix) with ESMTP id 869AE3BBBB90
 for <freebsd-stable@freebsd.org>; Wed,  1 Feb 2017 05:57:21 -0800 (PST)
Date: Wed, 1 Feb 2017 07:16:28 -0700 (MST)
From: Jakub Lach <jakub_lach@mailplus.pl>
To: freebsd-stable@freebsd.org
Message-ID: <1485958588529-6164674.post@n6.nabble.com>
In-Reply-To: <1485957121778-6164672.post@n6.nabble.com>
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>
Subject: Re: FreeBSD 11.0-STABLE #0 r310265 amd64 seems to be cpi-ing
 garbage to mounted FAT32 fs after 10-20 GB.
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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:16:31 -0000

I'm not sure if it's the same thing. Most of the times the corruption was
silent
then. 

Nonetheless, the outcome was the same after newfs HDD with UFS2-

http://www.pastebin.ca/3762661

I would 'blame' USB now, if only I did not migrate/clone the whole system to
SSD
via dump/the same USB not very long ago??



--
View this message in context: http://freebsd.1045724.x6.nabble.com/FreeBSD-11-0-STABLE-0-r310265-amd64-seems-to-be-cpi-ing-garbage-to-mounted-FAT32-fs-after-10-20-GB-tp6154963p6164674.html
Sent from the freebsd-stable mailing list archive at Nabble.com.