Dmitry Litvintsev

One thing I suggest to try. Change `storage-authzdb` so it looks like: ``` authorize atlagrid read-write 3327 124 / /pnfs/in2p3.fr/data/atlas / authorize cmsgrid read-write 3033 119 / /pnfs/in2p3.fr/data/cms / authorize...

Yes. we were under impression that this was been properly handled. I am just suggesting a mitigation. I believe that in path defined in storage-authzdb XRootD and WebDAV will work...

But yes, you are right. Since this issue concerns REST API only and this is sort of "experimental" feature, it is safer to wait for proper resolution.

I think this is a bug that affects everybody who use `xxx.root` property. NB at Fermilab we don't we prefer to have it defined in `/etc/grid-security/storage-authzdb`. We will investigate. This...

I think `gfal-xattr` calls `archiveinfo` of REST API While you at it - can you check if any operations in "our API" , say namespace fail with relative path. If...

on CMS T1 system: @ageorget @kofemann @stlammel It works for us. On CMS T1 tape: ``` frontend.root = /pnfs/fs/usr/cms webdav.root = /pnfs/fs/usr/cms ``` storage-authzdb: ``` authorize cmsprod read-write 9811 5063,9114,9247...

This is the best indication that there is load pattern that sculpts the initially random distribution. Do you have other activities on destination pools? That may sculpt the initially random...

Hi Onno, @paulmillar may correct me, but this looks similar to what was observed before - ability to read from directories if storage scope is not present. Which, I believe...

From doc (https://www.dcache.org/manuals/Book-9.2/config-xrootd.shtml#proxying-transfers-through-the-door): ``` If the door uses proxying, then when an open request arrives, a proxy instance will be launched on a new port and the client redirected to...

_might_ or you are actually impacted?