That may be true, but I'm pretty sure that in this case it simply has to do with the block size being requested.

I changed our client to use 8 MiB (like xrdcp) instead of 4, and it now works against RAL.

Al



________________________________
From: Andrew Hanushevsky ***@***.***>
Sent: Friday, August 6, 2021 3:15 PM
To: xrootd/xrootd ***@***.***>
Cc: Albert Rossi ***@***.***>; Comment ***@***.***>
Subject: Re: [xrootd/xrootd] 5.2.X xroot TPC transfer: File size mismatch in transfers to dcache (#1454)


Hi Paul,

I believe the reason is that xrdcp does not read past EOF (i.e. it gets
the size of the file first).

Andy


On Fri, 6 Aug 2021, Paul Millar wrote:

> At the risk of asking a stupid question: why is xrdcp able to transfer the file's content with the correct file size?
>
> I may be missing something, but dCache's embedded xrootd client and xrdcp are (in essence) doing the same thing: downloading a file. The difference is that xrdcp writes the correct number of bytes to disk while dCache's embedded client writes the wrong file size.
>
> If RAL's data server is somehow "wrong" (sending a final response with kXR_oksofar and some bogus response with kXR_ok) why does the transfer work for xrdcp?
>
> --
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1454#issuecomment-894164785<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_xrootd_xrootd_issues_1454-23issuecomment-2D894164785&d=DwQCaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=60rQ0HHqHmEY1P6VSdyuTQ&m=ZK1nXz6-BvxEqCOjH-uOt0hboJf_uH7nxFpb_Ijr5gQ&s=-SlYD6QEho3Tb3a6ChTbvRNwW8m2aZfYG6puzV_vXVo&e=>

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_xrootd_xrootd_issues_1454-23issuecomment-2D894496331&d=DwMCaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=60rQ0HHqHmEY1P6VSdyuTQ&m=ZK1nXz6-BvxEqCOjH-uOt0hboJf_uH7nxFpb_Ijr5gQ&s=ssM3nB15elbGN6Yb9nHSyUDW7NCqGew3X8DgAu9JByA&e=>, or unsubscribe<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AA6NBHAN6ZST7EN7KMDC6KTT3Q7HNANCNFSM44JDUM5A&d=DwMCaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=60rQ0HHqHmEY1P6VSdyuTQ&m=ZK1nXz6-BvxEqCOjH-uOt0hboJf_uH7nxFpb_Ijr5gQ&s=SGiSuwi3UdlXfW0eKVXTpFXDd12wR9Ny-uG9PJ18HnI&e=>.
Triage notifications on the go with GitHub Mobile for iOS<https://urldefense.proofpoint.com/v2/url?u=https-3A__apps.apple.com_app_apple-2Dstore_id1477376905-3Fct-3Dnotification-2Demail-26mt-3D8-26pt-3D524675&d=DwMCaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=60rQ0HHqHmEY1P6VSdyuTQ&m=ZK1nXz6-BvxEqCOjH-uOt0hboJf_uH7nxFpb_Ijr5gQ&s=t1OqN1XXv0gOvYYePesdjzo-NbSkOcWezS3wXx5dKHI&e=> or Android<https://urldefense.proofpoint.com/v2/url?u=https-3A__play.google.com_store_apps_details-3Fid-3Dcom.github.android-26utm-5Fcampaign-3Dnotification-2Demail&d=DwMCaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=60rQ0HHqHmEY1P6VSdyuTQ&m=ZK1nXz6-BvxEqCOjH-uOt0hboJf_uH7nxFpb_Ijr5gQ&s=0U5OODR0a2XAMKlS6zw2LflNpGYYZ5mLzA1UNVADYEY&e=>.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

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