Hi Lukasz,
With the client dump level I saw that it can happen that client is
closed before Detach() finishes:
https://github.com/xrootd/xrootd/blob/xrdposixcl/src/XrdPosix/XrdPosixFile.cc#L88
and that the thread which reads (prefetches) via the client is not yet
stopped.
The error makes sense and I know now how to handle it.
Thanks,
Alja
On 09/27/13 09:21, Lukasz Janyst wrote:
> Hi Alja,
>
> it's either an internal error or a memory corruption on your side.
> Could you please send a more detailed log? Dump mode would be the best.
> Greping for file name should give enough info. Does the error happen
> just after you open the file?
>
> Cheers,
> Lukasz
>
> On 27.09.2013 18:11, Alja Mrak Tadel wrote:
>> Hi,
>>
>> Sometimes I get the following error after successfully open the file in
>> the middle of reading file with XrdCL::File::Read():
>>
>> [2013-09-26 13:59:51 -0700][Error ][XRootD ]
>> [cmsstor364.fnal.gov:1093] Handling error while processing : [ERROR]
>> Error response.
>> [2013-09-26 13:59:51 -0700][Error ][File ]
>> [0xa0000e30@root://xrootd.unl.edu:1094//store/data/Run2012B/SingleElectron/AOD/22Jan2013-v1/20000/D0793DD1-FA7C-E211-8D4A-C860001BD882.root?oss.lcl=1]
>>
>> Fatal file state error. Message returned with [ERROR] Server responded
>> with an error: [3004] read does not refer to an open file
>>
>> What is best thing to do in this case? Cancel reading of the file or
>> make a new attempt with increased timeout?
>>
>>
>> Thanks,
>> Alja
>>
>> ########################################################################
>> 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
>
########################################################################
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
|