Opened 8 years ago

Closed 8 years ago

#75 closed task (fixed)

Synchronisation of IGCM files

Reported by: mafoipsl Owned by: mafoipsl
Priority: major Milestone: IPSLCM6
Component: Shared files Version: rc0
Keywords: IGCM ERGON TGCC IDRIS WORK Cc:

Description

Synchronisation of IGCM files is required. It's the firsttime we have to synchronise TGCC/WORK and IDRIS/ERGON.

Change History (4)

comment:1 Changed 8 years ago by mafoipsl

First, I synchronized IGCM between TGCC/WORK and ADA/WORK.

ipsl@curie> cd $WORKDIR
ipsl@curie> ./synchro_cccwork_to_ada

Second, I launched ADA/WORK ERGON synchronisation. More than 10 000 files have to be synchronized; It'll take some time.

ipsl@ergon>  ./synchro_ada_to_ergon

comment:2 Changed 8 years ago by jgipsl

Did the synchronization ./synchro_ada_to_ergon finish?

I've added files at curie/work and syncrhonized them to ada/work. But the syncronization to ciclad and ergon failed.

  • at ada: ./synchro_ada_to_ergon : permission denied
  • at ada: ./synchro_ada_to_ergon request for password : rpsl035@ada's password
  • or at ergon: ./synchro_ada_to_ergon request for password : rpsl035@ada's password

The folders concerned that are not synchronized are found in IGCM/BC/OOL/OL2/CRU-NCEP/: Folder v5.3 should be added and v5 removed.

comment:3 Changed 8 years ago by mafoipsl

Yes ./synchro_ada_to_ergon finished.

I complete the synchronisation with ciclad:

ipsl@ada> ./synchro_ada_to_ciclad

This synchronisation finished too.

comment:4 Changed 8 years ago by aclsce

  • Resolution set to fixed
  • Status changed from new to closed

Fichiers ajoutés ou modifiés sur le dépôt principale: Effectuer les 3 synchronisations depuis curie p86ipsl $WORKDIR. Les 3 synchronisations sont indépendants et peuvent être fait au même temps depuis 3 terminaux.

cd /ccc/work/cont003/dsm/p86ipsl
./synchro_cccwork_to_ada
./synchro_cccwork_to_ergon
./synchro_cccwork_to_ciclad

Plus d'infos là : http://wiki.ipsl.jussieu.fr/EsciComptes#Proc.2BAOk-dure_de_synchronisation_des_d.2BAOk-p.2BAPQ-ts_IGCM

Note: See TracTickets for help on using tickets.