> -----Original Message-----
> From: GRIDPP2: Deployment and support of SRM and local storage
> management [mailto:[log in to unmask]]On Behalf Of Colin
> Morey
> Sent: 06 October 2006 08:42
> To: [log in to unmask]
> Subject: Removing a pool node from a dcache system
>
>
> I have 3 empty pool nodes that I want to remove from the headnode
> completely,
> I've verified that there are no files in the psql db for those nodes
> with,
> =[1],[2]=
> $ cd /path/to/dcache/pool/data/
> $ for id in `ls -1 0*`;do rm -f `/path/to/pathfinder2 $id`;done
> ==
>
> i've set the three pools to disabled with[3],
> psu set disabled <pool>
>
>
> as the nodes are already empty, i haven't done step 2 from [3],
> I've shutdown the dcache-pool service on the 3 pools, however i'm not
> sure where i need to run `pnfs unregister`, is that in the ssh admin
> interface in `cd <pool name`
Yes, but if they're empty then its probably not needed - there are no entries to unregister. But it wouldn't hurt of course. You can also verify there are no entries by connecting to the companion database and doing SQL queries.
>
> Are there any other steps to removing a dcache-pool node from the
> config, [4] suggests that
> /opt/d-cache/config/`hostname`.poollist should
> be non-empty, but,
> ==
> ls -al /opt/d-cache/config/dcache02.poollist
> -rw-r--r-- 1 root root 0 Sep 13
> 11:42 /opt/d-cache/config/dcache02.poollist
> ==
>
If you're removing all the pools from a system, then the poollist file will be empty.
Derek
|