Closed ddavila0 closed 1 year ago
Hi @abh3 , I tried creating an already existing directory with the 'xroot' protocol instead and got a "File exist" which is the expected behavior.
[root@143e9b594cb7 tpc_transfers]# gfal-mkdir root://redirector.t2.ucsd.edu:1094//store/user/ddavila/newdir-001/
gfal-mkdir error: 17 (File exists) - Failed to create directory root://redirector.t2.ucsd.edu:1094//store/user/ddavila/newdir-001/ (File exists)
I also noticed that the error is different between XRootD v4 and v5. The error message that I showed in the post above is from V4. This is what I get from v5:
[root@143e9b594cb7 tpc_transfers]# gfal-mkdir davs://redirector.t2.ucsd.edu:1094/store/user/ddavila/newdir-001/
gfal-mkdir error: 5 (Input/output error) - HTTP 500 : Unexpected server error: 500 with url davs://redirector.t2.ucsd.edu:1094/store/user/ddavila/newdir-001/
so: v4 -> 404 File not found v5 -> 500 Unexpected server error
believe this has been fixed. in 5.4.3 If not please reopen tis.
Sorry for the duplicated post. I already reported this in an already merged PR[1] that seems related to this issue.
I think the issue fixed in the aforementioned PR[1] is still happening at the redirector level, when the redirector is optimized to do the lookup of the file/directory instead of redirecting the request. For example, this configuration triggers the issue:
cms.dfs lookup central mdhold 20m
and this doesn'tcms.dfs lookup distrib mdhold 20m redirect immed
Here there is an example of what you'll see when trying to create an already existing directory with gfal-mkdir:
We saw this in versions: 4.12.3-1 and 5.0.2-1 [1] https://github.com/xrootd/xrootd/pull/1164