Yes, I thought that addpool was adding hosts instead a pool is a cluster
of hosts/rfiod in DPM.
I subscribed the savannah bug.
thanks
cheers
alessandra
Greig Alan Cowan wrote:
> Hi Alessandra,
>
> The string that you specify with the --poolname option is the name
> that you have given to the pool to which you want to add the
> filesystem. As an example, at Edinburgh we have
>
> $ dpm-qryconf
> ...
> POOL lhcb DEFSIZE 0 GC_START_THRESH 0 GC_STOP_THRESH 0 DEF_LIFETIME
> 7.0d DEFPINTIME 2.0h MAX_LIFETIME 1.0m MAXPINTIME 12.0h FSS_POLICY
> maxfreespace GC_POLICY lru RS_POLICY fifo GIDS 104,103 S_TYPE -
> MIG_POLICY none RET_POLICY R
> CAPACITY 15.32T FREE 41.95G ( 0.3%)
> pool1.glite.ecdf.ed.ac.uk /gridstorage005 CAPACITY 1.79T FREE 37.69G
> ( 2.1%)
> pool1.glite.ecdf.ed.ac.uk /gridstorage006 CAPACITY 1.79T FREE 96.96G
> ( 5.3%)
> pool1.glite.ecdf.ed.ac.uk /gridstorage010 CAPACITY 1.79T FREE 1.60T
> ( 89.2%)
> pool1.glite.ecdf.ed.ac.uk /gridstorage011 CAPACITY 1.82T FREE 1.72T
> ( 94.5%)
> pool1.glite.ecdf.ed.ac.uk /gridstorage012 CAPACITY 1.82T FREE 1.72T
> ( 94.5%)
> ...
>
> To add a filesystem to this pool (called lhcb) I would do
>
> $ dpm-addfs --poolname lhcb --server pool1.glite.ecdf.ed.ac.uk --fs
> /gridstorage100
>
> This assumes that /gridstorage100 exists on the pool1 server and that
> the pool1 server has the rfiod daemon running.
>
> YAIM only supports the addition of a single pool by specifying its
> name in site-info.def (DPMPOOL option). This is something which I have
> brought up before and mentioned to John earlier in the week.
>
> https://gus.fzk.de/pages/ticket_details.php?ticket=24927
>
> Other pools have to be added by hand (or use a different
> site-info.def). It should be simple enough for you to wrap
> dpm-addpool and dpm-addfs in a shell script loop.
>
> Hope that clears things up.
>
> Cheers,
> Greig
>
> On 20/08/08 20:36, Alessandra Forti wrote:
>> Hi,
>>
>> I need a clarification...
>>
>> I'm trying to run dpm-addfs and I've lost two hours trying to run it
>> using any name as argument for the option --poolname
>> As I thought it was "just a name" and could be common to all the
>> pools something like "atlas_pool" or "dpm_bohr". Turns out that that
>> is not the case. Infact:
>>
>> /opt/lcg/bin/dpm-addfs --poolname dpm_bohr --server
>> bohr3215.tier2.hep.manchester.ac.uk --fs /data2
>> dpm-addfs dpm_bohr bohr3215.tier2.hep.manchester.ac.uk /data2:
>> Invalid argument
>>
>> while
>>
>> /opt/lcg/bin/dpm-addfs --poolname bohr3215 --server
>> bohr3215.tier2.hep.manchester.ac.uk --fs /data2
>>
>> works.
>>
>> Now this turns nasty if one uses YAIM because DPMPOOL needs to be
>> defined for each pool. i.e. it means a different site-info.def for
>> each pool.
>>
>> Could you tell me if this is the grim reality or if I'm doing
>> something wrong? I'm trying to automatize, so if I don't write N
>> different files I'll have to introduce some editing dependent on the
>> host name.
>>
>> cheers
>> alessandra
>>
--
Well you'll still need a tray
|