Seagate ST34572WC Specifications Page 16

  • Download
  • Add to my manuals
  • Print
  • Page
    / 36
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 15
6. Replacing the Disk
If you decide to replace the disk, you must perform a five-step procedure. How you perform each step depends on
the information you gathered earlier (hot-swap information, logical volume names, and recovery strategy), so this
procedure varies.
This section also includes several common scenarios for disk replacement, and a flowchart summarizing the disk
replacement procedure.
The five steps are:
1. Temporarily halt LVM attempts to access the disk.
2. Physically replace the faulty disk.
3. Configure LVM information on the disk.
4. Re-enable LVM access to the disk.
5. Restore any lost data onto the disk.
In the following steps, pvname is the character device special file for the physical volume. This name might be
/dev/rdsk/c2t15d0 or /dev/rdsk/c2t1d0s2.
Step 1: Halting LVM Access to the Disk
This is known as detaching the disk. The actions you take to detach the disk depend on whether the data is
mirrored, if the LVM online disk replacement functionality is available, and what applications are using the disk. In
some cases (for example, if an unmirrored file system cannot be unmounted), you must shut down the system.
If the disk is not hot-swappable, you must power down the system to replace it. By shutting down the
system, you halt LVM access to the disk, so you can skip this step.
If the disk contains any unmirrored logical volumes or any mirrored logical volumes without an available
and current mirror copy, halt any applications and unmount any file systems using these logical volumes.
This prevents the applications or file systems from writing inconsistent data over the newly restored
replacement disk. For each logical volume on the disk:
o If the logical volume is mounted as a file system, try to unmount the file system.
# umount /dev/vgname/lvname
Attempting to unmount a file system that has open files (or that contains a user’s current working
directory) causes the command to fail with a Device busy message. You can use the following
procedure to determine what users and applications are causing the unmount operation to fail:
1. Use the fuser command to find out what applications are using the file system as
follows:
# fuser -u /dev/vgname/lvname
This command displays process IDs and users with open files mounted on that logical
volume, and whether it is a user’s working directory.
2. Use the ps command to map the list of process IDs to processes, and then determine
whether you can halt those processes.
16
Page view 15
1 2 ... 11 12 13 14 15 16 17 18 19 20 21 ... 35 36

Comments to this Manuals

No comments