Print

Print

Aha ... what does xrdpc_print says about the cinfo file?

If file open request comes on top of a close (and especially if a new open comes when a file is already opened), xrootd might merge the two accesses and xcache will only see a single access, but the data-counters will show the correct amount of data transferred. Also, cache closes the file internally asynchronously, so it can reuse the file object for another IO-object if it comes in bbefore the acutal close happens ... in this case it will report N_ios correctly in cinfo -- in g-stream this is access_cnt

So, can you check all the g-stream records and see if some of them (presumably 10 :) ), contain either:
a) access_cnt > 0, or
b) b_hit + b_miss + b_bypass > test_file_size.

—
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/1525#issuecomment-936541049", "url": "https://github.com/xrootd/xrootd/issues/1525#issuecomment-936541049", "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