I looked into this some more. Apparently, it is not a kernel issue. What
xrootd is complaining about is that it should have had an available buffer
to do the I/O request but there was not one to be found. I'm not sure what
this indicates exactly since it's one of those conditions that should
never happen. As xrootd found itself in an untenable situation it threw
up it's hands and terminated your request.
On Wed, 12 Oct 2005, Fabrizio Furano wrote:
> Hi Andy,
> copying files with xrdcp I got this error from the kan cluster:
> 051012 09:04:16 14869 Xrd: ReadBuffer: Server
> [kan007.slac.stanford.edu:1094] did not return OK message for last
> 051012 09:04:16 14869 Xrd: SendGenCommand: Server declared error
> 3008:XrdXrootdAio: Unable to
> read /store/PRskims/R14/14.4.2a/BToDlnu/04/BToDlnu_0416.03HUBCA.root; No
> buffer space available
> To me it sounds ugly. It happened approaching the end of this copy. What do you think?