IBM TS7650G PROTECTIER DEDUPLICATION GATEWAY, Руководство пользователя

Страница: 197 / 248

7. On the active node, shut down the vtfd and ptcluster services in the
following order:
# service vtfd shutdown
# service ptcluster shutdown
Attention: Make sure to use the shutdown option and not the stop option. If
you use stop, the services restart automatically if a reboot occurs.
8. Start the
cman
and
clvmd
services in the following order:
# service cman start
# service clvmd start
9. For each of the problematic file systems, run the gfs_fsck –yv command in
the background with high verbosity and direct the output to a file:
# gfs_fsck -yv logical volume name > /pt_work/vgxx_fsck.out 2>&1 &
For example, the following command runs gfs_fsck on the logical volume
/dev/mapper/vg0-lv_vg0:
# gfs_fsck -yv /dev/mapper/vg0-lv_vg0 > /pt_work/vg0_fsck.out 2>&1 &
The output is saved in the file " /pt_work/vg0_fsck.out ."
Note: ProtecTIER supports up to 10 parallel gfs_fsck instances.
10. When all the gfs_fsck processes are complete, remove the
/etc/pt/dont_start_vtfd
and
/etc/pt/dont_start_ptcluster
so that these
services begin again when you restart the node.
# rm –f /etc/pt/dont_start_vtfd
# rm –f /etc/pt/dont_start_ptcluster
11.
Restart the node.
# reboot –nf
12. Restart the inactive node.
ProtecTIER is now up and running.
13. Send the fsck output to trained ProtecTIER specialist to determine the next
step.
Checking and repairing with ProtecTIER Manager
After any problematic file systems have been repaired, scan the ProtecTIER system
for errors, and attempt to repair them, using the Check and recover wizard.
Notes:
v For v3.3 and earlier, the check and recovery process is time-consuming and the
ProtecTIER system goes offline for the duration of the process. IBM therefore
recommends that you use the Check and recover wizard only for severe
problems.
v ProteTier v3.4 introduces a new feature, Near-Online check and recovery. This
feature reduces the downtime of ProteTIER during check and recovery by
enabling a continuous backup flow for most of the process. See “Near online
check and recovery” on page 179.
Checking the system
Complete this task to check the system for errors.
Chapter 17. Troubleshooting
177