On 30.01.2014 12:18, Adrian Sevcenco wrote:
>> The output of 'query space' is implementation dependent. In pure
>> xrootd you get:
>>
>> ]==> xrdfs metaman query space /data 2 13 31 2 13 31
>>
>> In EOS you get:
>>
>> ]==> xrdfs eosatlas query space /
>> oss.cgroup=default&oss.space=18747277867692032&oss.free=4341978005811200&oss.maxf=68719476736&oss.used=14405299861880832&oss.quota=18747277867692032
> hmm, this would be nice to get ..
Andy?
>> Isn't it what you need, except that in MB and %?
> nope .. i have 222 TB of data (now is less because of down dataserver)..
> you can see details here:
> http://alimonitor.cern.ch/stats?filter_0=ISS&page=SE%2Ftable
>
> So, the output is not correct..
It is correct, it just returns the info about the manager node and
not the whole cluster.
> the thing is that i understood that xrdfs should be the preferred method
> for xrood interrogation so this is why i try with xrdfs..
You're correct.
> in the mean time i will use this:
> echo exit | ~/xrdserver/bin/xrd $1.spacescience.ro queryspace / -
>
> as it give me some information
Again, thanks for pointing this out. This command does nothing more
than recursively sending the 'query space' to all the nodes in your
cluster and summing up the results. It is however unreliable, because it
does not take into account the implementation differences. We will look
into implementing this in a reliable way.
Cheers,
Lukasz
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1
