This looks rather strange. Can you make branch in your clone and push all your changes there, this code fragment seems inconsistent. What version are you using?

Corrupted access record check has a comment how strange things were happening to cinfo files on UCSD StashCache (I don't remember really tracing down what was causing it). This check is only done when reading older versions of cinfo files ... the new version stores checksum so we know if any part of cinfo gets corrupted. How did you get older versions of cinfo files on your setup?

Once we figure out the rest, I'd be interested in seeing if the ioActive ... called on a closed file is still around. As the error says, this really should not happen and has never been reported before. Is it possible you have some libraries mixed up from your build / system version? If you are running xrootd out of a build directory, you basically just need PATH=<path-to-builddir>/src:$PATH as things get built with -rpath option to linker.

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