Personal tools
You are here: Home Documentation Handbook Preparing a Pool for Removal
Document Actions

Preparing a Pool for Removal

by admin last modified 2007-08-03 02:26

The proper tools for preparing a pool for removal have not yet been written. This page is a substitute for proper methods, and only applies to the Nebraska T2 site.

Temporary Removal

To remove a pool temporarily (will be back in a couple of hours), do the following:
  • Touch /etc/stop_replicas on the dcache-head.unl.edu.  This is like /etc/nologin, except for the dCache PFM which controls the replication.  This will avoid massive replication of the node's old files.
  • Shut down dCache on the pool with /opt/d-cache/bin/dcache-pool stop.
  • Turn off the pool.
After the pool is ready to go back online, all you have to do is remove the /etc/stop_replicas file.

Permanent Removal

This is an operation I'll eventually create a specialized tool for.  Until then, do the following:
  1. Look at the last entries for zero replica files in /home/brian/projects/dCacheNebraska/scripts/zerorep_logfile.
  2. Add the pool name to the blacklist  in /home/brian/projects/dCacheNebraska/scripts/pfm_config.
  3. Run dcache_pfm.py manually or let it run automatically over the course of a couple hours.
  4. Repeat step (3) until the list of zero replicas that dcache_pfm.py outputs is the same as it was in (1).
The whole point of having a PFM is that we can lose any pool at any time, so technically none of these steps are necessary (but who's going to trust a computer to do something right?).  Make sure that any files you don't want to lose are, for now, protected by the PFM by having multiple replicas.

Powered by Plone, the Open Source Content Management System