David Holland wrote: >On Mon, Aug 03, 2015 at 02:51:37PM -0700, Jeff Rizzo wrote: > > I need to look deeper, but a quick test writing lines of > > ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz > > > > Shows that corruption starts when the file is exactly 65536 bytes long > > (with an 8192 byte page size), with anything that size or longer getting > > corrupted. It seems to be randomly garbled - same size, same bytes, but > > shuffled around. When I was narrowing it down, I sometimes saw random > > corruption inserted at larger file sizes - at one point I saw short strings > > of NUL and the string "posix2_upe" (which would appear to be a symbol?) > > inserted at seemingly-random spots. > >Does that size vary with the NFS block size?
Also is it using UDP or TCP ? >The symptoms make me think of scrambled mbufs, if anything... My guess is that the panics that wiz and I saw in the checksum code on amd64 were also due to scrambled mbufs. My cubietruck seems fine using awge(4), I have built a fair number of packages over NFS recently. Robert Swindells
