I don't know if it's useful, but I ran this through strace and found the following:
```
[pid 3139] epoll_wait(149, {{EPOLLIN, {u32=3628045120, u64=140350274376512}}}, 1024, 4294967295) = 1
[pid 3139] read(168, "\0\0\0\0", 16) = 4
[pid 3139] read(168, 0x7fa5d8c741cc, 12) = -1 EAGAIN (Resource temporarily unavailable)
[pid 3139] read(168, "\0\1p$\0\0\0\0\200M\3363", 12) = 12
[pid 3139] gettimeofday({1398314925, 998294}, NULL) = 0
[pid 3139] write(2, "[2014-04-24 06:48:45 +0200][Dump"..., 151[2014-04-24 06:48:45 +0200][Dump ][XRootD ] [red-gridftp4.unl.edu:1094] ReadRawReadV: read buffer for chunk 611320064@3737509952915243008
) = 151
[pid 3139] gettimeofday({1398314925, 998443}, NULL) = 0
[pid 3139] epoll_wait(149, {{EPOLLIN, {u32=3628045120, u64=140350274376512}}}, 1024, 4294967295) = 1
[pid 3139] read(168, "\0\0\0\327\3\354\0\0\1TF\344\32J\0{", 16) = 16
[pid 3139] gettimeofday({1398314925, 998624}, NULL) = 0
[pid 3139] write(2, "[2014-04-24 06:48:45 +0200][Erro"..., 185[2014-04-24 06:48:45 +0200][Error ][XRootD ] [red-gridftp4.unl.edu:1094] ReadRawReadV: Impossible to find chunk buffer corresponding to 65798144 bytes at 95779437589168251.
```
All the cases where an invalid request was returned had the read of the header split across. The problem can't be that simple though - there were cases where the header was split but didn't run into an invalid argument error. That said, most of those cases look like this:
```
[pid 29963] read(161, "\0\0\0\0\0\1+!\0\0\0\0", 16) = 12
[pid 29963] read(161, 0x7fa36781b3d4, 4) = -1 EAGAIN (Resource temporarily unavailable)
[pid 29963] read(161, 0x7fa36781b3d4, 4) = -1 EAGAIN (Resource temporarily unavailable)
[pid 29963] gettimeofday({1398309237, 668923}, NULL) = 0
[pid 29963] epoll_wait(148, {{EPOLLIN, {u32=1823182080, u64=140339879578880}}}, 1024, 4294967295) = 1
```
---
Reply to this email directly or view it on GitHub:
https://github.com/xrootd/xrootd/issues/45#issuecomment-41281982
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
