36.2 Cleaning Up Linux Workloads

The following are instructions for cleaning up Linux workloads by component and use case.

Table 36-2 Use Cases and Instructions for Cleaning Up Linux Workloads

Component

Use Case

Removal Instructions

Controller software

All migrations

  1. Stop the OFX controller process:

    /etc/init.d/ofxcontrollerd stop

  2. Remove the OFX controller service:

    chkconfig --del ofxcontrollerd

  3. Clean up the OFX controller files:

    • rm -rf /usr/lib/ofx

    • rm -f /etc/init.d/ofxcontrollerd

Block-level data transfer software

All block-level migrations

  1. Check if the driver is active:

    lsmod | grep blkwatch

    If the driver is still loaded in memory, the result should contain a line, similar to the following:

    blkwatch_7616  70924  0

  2. (Conditional) If the driver is still loaded, remove it from memory:

    rmmod blkwatch_7616

  3. Remove the driver from the boot sequence:

    blkconfig -u

  4. Remove the driver files by deleting the following directory with its contents:

    rm -rf /lib/modules/<kernel-version>/platespin

    For example:

    rm -rf /lib/modules/3.0.101-63-default/platespin

    You can alternately use a variable $(uname -r) to dynamically retrieve the kernel version for the directory name:

    rm -rf /lib/modules/$(uname -r)/platespin

  5. Delete the following file:

    /etc/blkwatch.conf

LVM snapshots

Block-level migrations using LVM snapshots

  1. In the Jobs view, generate a Job Report for the failed job, then note the name of the snapshot.

  2. Remove the snapshot device by using the following command:

    lvremove snapshot_name