Andrew Elwell wrote:
>> What's the name of the "node type" for DPM disk servers /pool nodes? I tried
>> this:
>>
>> /*/opt/glite/yaim/bin/yaim -c -s site-info_4.0.x.def -n glite_SE_dpm_disk*/
>> /*ERROR: One of the functions returned with error without specifying it's
>> nature !*/
>>
>
> taken from
> https://twiki.cern.ch/twiki/bin/view/LCG/GenericInstallGuide310
>
> glite-SE_dpm_disk (first one is a dash not an underscore)
>
thanks Andrew, that solves the "hang out" problem but now I see these in
the end:
WARNING: Failed to add filesystem /dpm_data1 to the pool ! May it is already part of the pool !
dpm-qryconf: Permission denied
dpm-addfs dpmCam_2009 disk06.hep.phy.cam.ac.uk /dpm_data2: Permission denied
dpm-qryconf: Permission denied
WARNING: Failed to add filesystem /dpm_data2 to the pool ! May it is already part of the pool !
net.ipv4.ip_forward = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
kernel.sysrq = 0
kernel.core_uses_pid = 1
net.ipv4.tcp_rmem = 131072 1048576 2097152
net.ipv4.tcp_wmem = 131072 1048576 2097152
net.ipv4.tcp_mem = 131072 1048576 2097152
net.core.rmem_default = 1048576
net.core.wmem_default = 1048576
net.core.rmem_max = 2097152
net.core.wmem_max = 2097152
net.ipv4.tcp_dsack = 0
net.ipv4.tcp_sack = 0
net.ipv4.tcp_timestamps = 0
net.core.netdev_max_backlog = 10000
ERROR: Error during the execution of function: config_DPM_disk
ERROR: Error during the configuration.Exiting. [FAILED]
ERROR: One of the functions returned with error without specifying it's nature !
I already have another pool (dpmCam_2007) running. Manually added the
new pool (dpmCam_2009) and the file system afterwards:
[root@serv02 ~]# dpm-qryconf
POOL dpmCam_2007 DEFSIZE 200.00M 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 0 S_TYPE - MIG_POLICY none RET_POLICY R
CAPACITY 37.52T FREE 12.55T ( 33.5%)
disk01.hep.phy.cam.ac.uk /dpm_data CAPACITY 7.50T FREE 6.82T ( 90.9%)
disk02.hep.phy.cam.ac.uk /dpm_data CAPACITY 7.50T FREE 6.85T ( 91.3%)
disk03.hep.phy.cam.ac.uk /dpm_data CAPACITY 7.50T FREE 6.87T ( 91.5%)
disk04.hep.phy.cam.ac.uk /dpm_data CAPACITY 7.50T FREE 6.81T ( 90.8%)
disk05.hep.phy.cam.ac.uk /dpm_data CAPACITY 7.50T FREE 6.81T ( 90.8%)
POOL dpmCam_2009 DEFSIZE 200.00M 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 0 S_TYPE V MIG_POLICY none RET_POLICY R
CAPACITY 10.00T FREE 10.00T (100.0%)
disk06.hep.phy.cam.ac.uk /dpm_data1 CAPACITY 5.00T FREE 5.00T (100.0%)
disk06.hep.phy.cam.ac.uk /dpm_data2 CAPACITY 5.00T FREE 5.00T (100.0%)
So, is my new dpm pool node sick?
Cheers,
Santanu
|