Tuesday, March 27, 2007

ATLAS DPM Pool at Glasgow Set "World Writable"

When I was poking around looking for lost DPM files last week I found a problem with our large dedicated ATLAS DPM pool. The problem is that the pool is restricted to one GID only, but different VOMS roles are mapped to different GIDs by DPM. So in fact we have:
mysql> select * from Cns_groupinfo where groupname like 'atlas%';
| rowid | gid | groupname |
| 2 | 103 | atlas |
| 16 | 117 | atlas/Role=lcgadmin |
| 17 | 118 | atlas/Role=production |
3 rows in set (0.00 sec)

So only "ordinary" ATLAS users were getting access to the big pool. ATLAS production was being relegated to the general pool! No wonder it had filled up so much:
POOL atlas
CAPACITY 27.22T FREE 23.04T ( 84.6%)
POOL generalPool
CAPACITY 6.81T FREE 2.68T ( 39.4%)
As the ATLAS data was split so evenly between regular and production use I decided to make the pool writable by all groups. Now, when DPM 1.6.4 is released we will want to switch the pool to be writable by all our ATLAS groups. This clearly leaves a lot of data misplaced. I have made a feature request to enhance dpm-drain to try and help sort the mess out.

No comments: