There are no checksums per se in other protocols. When using TLS is a
block cannot be decrypted (i.e. the internal checksum doesn't match) then
TLS simply closes the connection. Non-TLS transfers always succeed as long
as the length isn't corrupted. So, I suppose none of this should be
suprising. As for the retry logic errfor, indeed, that was a bug taht got
corrected in 5.5.2. When correction occurs, it is expected that the
transfer rate will slow as corrections occur in single 4k page units. That
bug causes a slew of corrections that definitely were not needed.

Andy

On Mon, 6 Feb 2023, Brian P Bockelman wrote:

> That's definitely a part of it! There's may be one more bug in the recovery logic as periodically the data transfer rate will drop to zero during these recovery periods.
>
> However, I'm not sure it solves my root issue: it's unclear why the checksums fail *only* when using the `pgread` API (and not when transferring with other protocols).
>
> --
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1893#issuecomment-1419240186
> You are receiving this because you are subscribed to this thread.
>
> Message ID: ***@***.***>

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1893#issuecomment-1419936740", "url": "https://github.com/xrootd/xrootd/issues/1893#issuecomment-1419936740", "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