BTY, the code has substantially changed in R5.1.0 so this problem may have
been fixed relative to you. I don't think this fix can be backported as
it's pretty extensive. Anyway, let's see what the developer says.
On Tue, 23 Feb 2021, Elvin Sindrilaru wrote:
> Thanks to Mihai from the FTS team, I managed to catch one such corrupted file and compared its contents with the correct one. I seems the beginning of every MB is corrupted, for example bytes that differ in this particular case are:
> 1MB -> 1MB + 5952
> 2MB -> 2MB + 6688
> 3MB -> 3MB + 5728
> ....
>
> 403MB -> 403MB + 15632
>
> I have the full info if this is necessary. The full size of the file is: 423436359 bytes
> Actual logs from the FST transfer:
> https://fts-pilot-010.cern.ch:8449/var/log/fts3/transfers/2021-02-23/webdav.lcg.triumf.ca__eosatlas.cern.ch/2021-02-23-0948__webdav.lcg.triumf.ca__eosatlas.cern.ch__1448324283__9c8bd9bc-75bb-11eb-bc6b-fa163e14af38
>
> In the meantime, similar errors were identified also in EOSATLAS with apparently a higher incidence rate once we moved to XRootD 4.12.7.
>
> --
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1404#issuecomment-784090544
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/1404#issuecomment-784109682",
"url": "https://github.com/xrootd/xrootd/issues/1404#issuecomment-784109682",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
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