Jakub Lach
2017-Feb-01 14:16 UTC
FreeBSD 11.0-STABLE #0 r310265 amd64 seems to be cpi-ing garbage to mounted FAT32 fs after 10-20 GB.
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.
Konstantin Belousov
2017-Feb-01 14:48 UTC
FreeBSD 11.0-STABLE #0 r310265 amd64 seems to be cpi-ing garbage to mounted FAT32 fs after 10-20 GB.
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.