OK in addition to the bisection I've collected trace data for the good
(commit 4d770ccf4257b23a7ca2a85de1b1c22657b581d8) and bad (commit
e261f51f25b98c213e0b3d7f2109b117d714f69d) cases.
Attached is a file called trace.tar.bz2 inside you'll find 4 files, for
the two sessions:
bad-wireshark
bad-strace
good-wireshark
good-strace
From a quick glance the difference seems to be the bad case does an
UNSTABLE NFS WRITE call. I don't really know what that means or what
its semantics are... but that bad commit does seem to introduce this
regression.
Anything else I can provide?
Thanks!
=a=
--
===================
Aaron Straus
aaron@merfinllc.com