 |
 |
Hi, Is it possible that your VO-dedicated pools are of, e.g., permanent type while the client trying to write in it is asking for volatile type (as rfcp or globus-url-copy do) and so the open pool is the only one matching? Antonio. Jeff Templon escribió: > Hi *, > > I am trying to figure out how DPM does its pool selection. In the DPM > manual, there is a statement that if a VO-specific pool exists, as > well as a general pool, the VO-specific pool will be used first. This > is not what is happening here. I see the following in the dpm log > file in /var/log/dpm/log: > > dpm_selectfs: selected pool: Volatile > > where Volatile is our "GID 0" pool. The Atlas-D pool is not getting > selected. How do I figure out why a certain pool is / is not getting > selected? Can I increase a logging level somewhere? > > It would also be nice if someone would write an actual DPM manual. I > tried looking at the documentation, but the Wiki structure is not > really amenable to understanding the DPM. > > JT > > ps: one more thing: the exact passage in the manual says: > >> If you define : >> one pool dedicated to group1 / VO1 >> one pool open to all groups / VOs >> then, the dedicated pool will be used until it is full. > > We have one pool dedicated to group1 > another pool to group2 > another pool to group3 > one pool open to all groups > > which is not *exactly* the same as what is described in the manual. > Is this just accidentally being too precise with words, or does it > really only work with a single vo-specific pool?