walker@heppc300:~$ lcg-info --list-se --vo t2k.org --query
'SE=se03.esc.qmul.ac.uk' --attrs
UsedNearline,UsedOnline,TotalOnline,TotalNearline
- SE: se03.esc.qmul.ac.uk
- UsedNearline 0
- UsedOnline 37786
- TotalOnline 100000
- TotalNearline 0
walker@heppc046:~$ ldapsearch -x -h lcgbdii.gridpp.rl.ac.uk -p 2170 -b
o=grid '(&(objectclass=GlueSA)(GlueChunkKey=GlueSEUniqueID=*.qmul.ac.uk)
(GlueSAAccessControlBaseRule=*t2k.org))' GlueSALocalID
GlueSATotalOnlineSize GlueSAFreeOnlineSize GlueSAUsedOnlineSize | grep
-A 2 GlueSALocalID:
GlueSALocalID: t2k.org:replica:online
GlueSAUsedOnlineSize: 0
GlueSATotalOnlineSize: 1000
--
GlueSALocalID: t2k.org:replica:online
GlueSAUsedOnlineSize: 0
GlueSATotalOnlineSize: 1000
--
GlueSALocalID: t2k.org:replica:online
GlueSATotalOnlineSize: 100000
GlueSAUsedOnlineSize: 37786
[root@se04 t2k.org]# du --summarize
39493616216 .
perl -e 'print 39493616216/1024/1024'
37664.0474472046
So that is pretty much right for QMUL. Any differences are probably my
fault, not yours.
See also comments inline:
On 19/10/12 06:28, Sam Skipsey wrote:
> Hm.
>
> Well, for DPM, the publishing in the BDII is always a bit off for VOs
> which share a single pool - the free space available published is that
> in the pool, which can end up double or triple counting for some cases
> (if you have a spacetoken, then it can publish the free space in the
> token where the token is published, which is more what people care
> about).
> I'd expect TotalOnline to be the total space *available* to T2K at
> RAL, on disks (and this is the figure that, for a shared pool, will be
> just the pool size).
> TotalUsed is the total amount of space consumed in that total online space.
>
> This doesn't explain the apparent shortfall of space used, compared to
> the claimed 300T...
>
> Sam
>
> On 18 October 2012 18:07, Jonathan Perkin <[log in to unmask]> wrote:
>> Hi all,
>>
>> I have written some crude auditing scripts that trawl the LFC, harvesting data on what files are replicated where. What I'd like to do is compare the results with what is actually on disk at a given site - however, this info eludes me.
>>
>> The guys at RAL have told me there is ~300TB of t2k.org data on srm-t2k.gridpp.rl.ac.uk, however the information service never seems to agree, presumably because there is always some mangling of actual usage and quota on the pool?
>>
>> Here's what I've tried so far:
>> #!/bin/bash
>>
>>
>> echo "LDAP SEARCH:"
>> ldapsearch -x -h lcgbdii.gridpp.rl.ac.uk -p 2170 -b o=grid \
>> '(&(objectclass=GlueSA)(GlueChunkKey=GlueSEUniqueID=srm*.gridpp.rl.ac.uk) (GlueSAAccessControlBaseRule=*t2k.org))' \
>> GlueSALocalID GlueSATotalOnlineSize GlueSAFreeOnlineSize \
>> GlueSAUsedOnlineSize | grep -A 2 GlueSALocalID:
>>
>> echo "INFO SERVICE"
>> lcg-info --list-se --query 'SE=srm-t2k.gridpp.rl.ac.uk' \
>> --attrs UsedNearline,UsedNearline,TotalOnline,TotalNearline
>>
Shouldn't one of those be UsedNearline be UsedOnLine?
In my example above, I also add --vo t2k.org
>> producing:
>> LDAP SEARCH:
>> GlueSALocalID: t2kTape
>> GlueSATotalOnlineSize: 17280
>> GlueSAUsedOnlineSize: 12095
>>
>> INFO SERVICE
>> - SE: srm-t2k.gridpp.rl.ac.uk
>> - UsedOnline 12095
>> 12095
>> - UsedNearline 652072
>> 0
>> - TotalOnline 17280
>> 17280
>> - TotalNearline 787197
>> 0
>>
>> You can get ~300TB by summing GlueSATotalOnlineSize: 17280 and GlueSAUsedOnlineSize: 12095 but this seems counter intuitive and if I do the same for t2ksrm.nd280.org the results are inconsistent (there is ~270TB there, according to their online monitor and this is covered entirely by GlueSAUsedOnlineSize: 290341)
>>
>> Any advice on where I am going wrong is most welcome!
>>
Chris
|