 |
 |
On Sun, 19 Dec 2004, Kurt Vanmechelen wrote: > Could somebody fill me in on the current status of : > 1) Consistency component of the RMS The high-level tools edg-rm, lcg-cr etc. try to prevent the user from introducing inconsistencies in the catalogs, but they are not (yet) completely safe in that respect (a rollback on error is not always done). AFAIK, there is no standard tool that will check the consistency of the catalogs and report dangling entries; problems are certainly not fixed automatically. > 2) Pro-active data replication done by the RMS That does not exist in the current RMS. Explicit replication commands have to be issued. Making the RMS pro-active is non-trivial. Do you have a use case? > Is this currently working, and if not, how would I go about updating a > 'master copy' of a file on the Grid for example? > Deregistering all old replica's and reregistering the updated file under > the same lfn? As Stephen said: files should be write-once. Data sets etc. should always have version numbers in their names, so that there is no *need* to update any files; obsolete versions can be deleted after a grace period. Deregistering *all* old replicas can be next to impossible on a grid: what would you do if one of the associated SEs/LRCs were down for a week?