Has anyone seen writev on FreeBSD return EINVAL after a write to a socket even though the data has hit the wire?

[Richard Sharpe]

Hi folks,

I am seeing a problem with SMB2 and writev's of responses, usually
large responses, like a 64kiB read response. writev is returning
EINVAL even though the data has actually hit the wire. I have verified
this by looking at the capture and comparing the SMB sequence number
in the header of the packet on the wire with what is in memory pointed
to by the iovec sent to writev.

It is most strange, and I am unable to think how this might happen.

-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)