Jakub Lach
2017-Feb-01 12:38 UTC
FreeBSD 11.0-STABLE #0 r310265 amd64 seems to be cpi-ing garbage to mounted FAT32 fs after 10-20 GB.
As it shows your interest, I appreciate your answer very much. I was a bit let down then, I had to (using the same card reader), cp -r using borrowed Apple iMac. It worked as it should. It was FreeBSD 11.0-STABLE #0 r310265 amd64 as in subject, I will reconsider retesting now and filling a PR, with a different data set and medium though. Thanks. -- 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-tp6154963p6164655.html Sent from the freebsd-stable mailing list archive at Nabble.com.
Konstantin Belousov
2017-Feb-01 12:50 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 05:38:07AM -0700, Jakub Lach wrote:> As it shows your interest, I appreciate your answer very much. > > I was a bit let down then, I had to (using the same card reader), > cp -r using borrowed Apple iMac. It worked as it should. > > It was FreeBSD 11.0-STABLE #0 r310265 amd64 as in subject, > I will reconsider retesting now and filling a PR, with a different > data set and medium though. Thanks.Does that happen on any device which carries FAT fs, or since you mentioned a card reader, does it happen with any other filesystem carried by a volume on the card ? In other words, why do you blame FAT and not the card reader ?