Date: Wed, 1 Feb 2017 16:48:35 +0200 From: Konstantin Belousov <kostikbel@gmail.com> 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: <20170201144835.GE2092@kib.kiev.ua> In-Reply-To: <1485958588529-6164674.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> <1485958588529-6164674.post@n6.nabble.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 01, 2017 at 07:16:28AM -0700, Jakub Lach wrote: > 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?? Note that in the paste above you get write errors reported, while the corruption happens while you read from the volume.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170201144835.GE2092>