Print

Print


I spent about an hour tinkering with different approaches to fixing the return code from the cmsd. However, it was quickly becoming a wholesale rewrite of all return codes between the server and client - it kept snowballing into pieces of the codebase I wasn't familiar with.

So, I agree with the idea that we really should fix the problem at the root.

That said - this is somewhat critical / urgent because it causes problems with the gfal2 recursive directory creation and causes failures in the corresponding FTS transfers. gfal2 will try a mkdir on each directory path, starting with the file's destination directory and walking up the tree until the return code switches from "file not found" to "file exists". Because Xrootd always returns ENOENT, gfal2 keeps walking up the tree until it hits a top-level directory (or ultimately /) and gets a permission error.

Given doing a reasonable fix looked like a large-scale project (which are best not rushed) -- and needing a short-term fix for 4.11.x -- led me to do the small patch based on error message. I sure hope we are long done with tinkering with error message texts for 4.11.x!


You are receiving this because you are subscribed to this thread.
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/1167#issuecomment-605511842", "url": "https://github.com/xrootd/xrootd/issues/1167#issuecomment-605511842", "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