Solstice Disk Suite 完全使用手册(EN版)

东方蜘蛛

Installing DiskSuite

The DiskSuite packages have moved around a bit with each release of Solaris. For Solaris 2.6 and Solaris 7, the DiskSuite packages are located on the Easy Access CD. With Solaris 8, DiskSuite moved to the "Solaris 8 Software" cdrom number two, in the EA directory. Starting the Solaris 9, DiskSuite is now included with the operating system.

At the time of this writing, Solaris 8 is the most commonly deployed version of Solaris, so we'll use that as the basis for this example. The steps are basically identical for the other releases.

1.After having completed the installation of the Solaris 8 operating system, insert the Solaris 8 software cdrom number two into the cdrom drive. If volume management is enabled, it will automatically mount to /cdrom/sol_8_401_sparc_2 (depending on the precise release iteration of Solaris 8, the exact path may differ in your case):

1. # df -k
   
2. Filesystem            kbytes    used   avail capacity  Mounted on
   
3. /dev/dsk/c0t0d0s0    6607349  826881 5714395    13%    /
   
4. /proc                      0       0       0     0%    /proc
   
5. fd                         0       0       0     0%    /dev/fd
   
6. mnttab                     0       0       0     0%    /etc/mnttab
   
7. /dev/dsk/c0t0d0s4    1016863    8106  947746     1%    /var
   
8. swap                 1443064       8 1443056     1%    /var/run
   
9. swap                 1443080      24 1443056     1%    /tmp
   
10. /vol/dev/dsk/c0t6d0/sol_8_401_sparc_2
    
11.                       239718  239718       0   100%    /cdrom/sol_8_401_sparc_2
    
12. 
    

复制代码

2.Change to the directory containing the DiskSuite packages:

1. # cd /cdrom/sol_8_401_sparc_2/Solaris_8/EA/products/Disksuite_4.2.1/sparc/Packages

复制代码

3.Add the required packages (we're taking everything except the Japanese-specific package):

1. # pkgadd -d .
   
2. 
   
3. The following packages are available:
   
4.   1  SUNWmdg      Solstice DiskSuite Tool
   
5.                   (sparc) 4.2.1,REV=1999.11.04.18.29
   
6.   2  SUNWmdja     Solstice DiskSuite Japanese localization
   
7.                   (sparc) 4.2.1,REV=1999.12.09.15.37
   
8.   3  SUNWmdnr     Solstice DiskSuite Log Daemon Configuration Files
   
9.                   (sparc) 4.2.1,REV=1999.11.04.18.29
   
10.   4  SUNWmdnu     Solstice DiskSuite Log Daemon
    
11.                   (sparc) 4.2.1,REV=1999.11.04.18.29
    
12.   5  SUNWmdr      Solstice DiskSuite Drivers
    
13.                   (sparc) 4.2.1,REV=1999.12.03.10.00
    
14.   6  SUNWmdu      Solstice DiskSuite Commands
    
15.                   (sparc) 4.2.1,REV=1999.11.04.18.29
    
16.   7  SUNWmdx      Solstice DiskSuite Drivers(64-bit)
    
17.                   (sparc) 4.2.1,REV=1999.11.04.18.29
    
18. 
    
19. Select package(s) you wish to process (or 'all' to process
    
20. all packages). (default: all) [?,??,q]: 1 3 4 5 6 7
    
21. 
    
22. Processing package instance <SUNWmdg>; from </cdrom/sol_8_401_sparc_2/Solaris_8/EA/products/DiskSuite_4.2.1/sparc/Packages>;
    
23. .
    
24. .
    
25. .
    
26. postinstall: configure driver
    
27. 
    
28.                 (This may take a while.)
    
29. 
    
30. Installation of <SUNWmdx>; was successful.
    
31. 
    
32. The following packages are available:
    
33.   1  SUNWmdg      Solstice DiskSuite Tool
    
34.                   (sparc) 4.2.1,REV=1999.11.04.18.29
    
35.   2  SUNWmdja     Solstice DiskSuite Japanese localization
    
36.                   (sparc) 4.2.1,REV=1999.12.09.15.37
    
37.   3  SUNWmdnr     Solstice DiskSuite Log Daemon Configuration Files
    
38.                   (sparc) 4.2.1,REV=1999.11.04.18.29
    
39.   4  SUNWmdnu     Solstice DiskSuite Log Daemon
    
40.                   (sparc) 4.2.1,REV=1999.11.04.18.29
    
41.   5  SUNWmdr      Solstice DiskSuite Drivers
    
42.                   (sparc) 4.2.1,REV=1999.12.03.10.00
    
43.   6  SUNWmdu      Solstice DiskSuite Commands
    
44.                   (sparc) 4.2.1,REV=1999.11.04.18.29
    
45.   7  SUNWmdx      Solstice DiskSuite Drivers(64-bit)
    
46.                   (sparc) 4.2.1,REV=1999.11.04.18.29
    
47. 
    
48. Select package(s) you wish to process (or 'all' to process
    
49. all packages). (default: all) [?,??,q]: q
    
50. 
    
51. *** IMPORTANT NOTICE ***
    
52.         This machine must now be rebooted in order to ensure
    
53.         sane operation.  Execute
    
54.                shutdown -y -i6 -g0
    
55.         and wait for the "Console Login:" prompt.
    
56. # eject cdrom
    
57. # shutdown -y -i6 -g0

复制代码

4.Once the system reboots, apply any DiskSuite patches. At the time of this writing, the latest recommended DiskSuite patch available from sunsolve.sun.com is 106627-18 (DiskSuite 4.2) or 108693-13 (DiskSuite 4.2.1). Note that the patch installation instructions require that a reboot be performed after the patch is installed.

[ 本帖最后由 东方蜘蛛 于 2007-3-19 09:23 编辑 ]

东方蜘蛛

Mirroring the operating system

In the steps below, I'm using DiskSuite to mirror the active root disk (c0t0d0) to a mirror (c0t1d0). I'm assuming that partitions five and six of each disk have a couple of cylinders free for DiskSuite's state database replicas.

Introduction

First, we start with a filesystem layout that looks as follows:

1. Filesystem            kbytes    used   avail capacity  Mounted on
   
2. /dev/dsk/c0t0d0s0    6607349  826881 5714395    13%    /
   
3. /proc                      0       0       0     0%    /proc
   
4. fd                         0       0       0     0%    /dev/fd
   
5. mnttab                     0       0       0     0%    /etc/mnttab
   
6. /dev/dsk/c0t0d0s4    1016863    8106  947746     1%    /var
   
7. swap                 1443064       8 1443056     1%    /var/run
   
8. swap                 1443080      24 1443056     1%    /tmp

复制代码

We're going to be mirroring from c0t0d0 to c0t1d0. When the operating system was installed, we created unassigned slices five, six, and seven of roughly 10 MB each. We will use slices five and six for the DiskSuite state database replicas. The output from the "format" command is as follows:

1. # format
   
2. Searching for disks...done
   
3. 
   
4. 
   
5. AVAILABLE DISK SELECTIONS:
   
6.        0. c0t0d0 <SEAGATE-ST19171W-0024 cyl 5266 alt 2 hd 20 sec 168>;
   
7.           /pci@1f,4000/scsi@3/sd@0,0
   
8.        1. c0t1d0 <SEAGATE-ST19171W-0024 cyl 5266 alt 2 hd 20 sec 168>;
   
9.           /pci@1f,4000/scsi@3/sd@1,0
   
10. Specify disk (enter its number): 0
    
11. 
    
12. selecting c0t0d0
    
13. [disk formatted]
    
14. ...
    
15. partition>; p
    
16. Current partition table (original):
    
17. Total disk cylinders available: 5266 + 2 (reserved cylinders)
    
18. 
    
19. Part      Tag    Flag     Cylinders        Size            Blocks
    
20.   0       root    wm       0 - 3994        6.40GB    (3995/0/0) 13423200
    
21.   1       swap    wu    3995 - 4619        1.00GB    (625/0/0)   2100000
    
22.   2     backup    wm       0 - 5265        8.44GB    (5266/0/0) 17693760
    
23.   3 unassigned    wu       0               0         (0/0/0)           0
    
24.   4        var    wm    4620 - 5244        1.00GB    (625/0/0)   2100000
    
25.   5 unassigned    wm    5245 - 5251       11.48MB    (7/0/0)       23520
    
26.   6 unassigned    wm    5252 - 5258       11.48MB    (7/0/0)       23520
    
27.   7 unassigned    wm    5259 - 5265       11.48MB    (7/0/0)  23520

复制代码

  


DiskSuite Mirroring

Note that much of the process of mirroring the root disk has been automated with the sdsinstall script. With the exception of the creation of device aliases, all of the work done in the following steps can be achieved via the following:

1. # ./sdsinstall -p c0t0d0 -s c0t1d0 -m s5 -m s6

复制代码

1.Ensure that the partition tables of both disks are identical:

1. # prtvtoc /dev/rdsk/c0t0d0s2 | fmthard -s - /dev/rdsk/c0t1d0s2

复制代码

2.Add the state database replicas. For redundancy, each disk has two state database replicas.

1. # metadb -a -f c0t0d0s5
   
2. # metadb -a c0t0d0s6
   
3. # metadb -a c0t1d0s5
   
4. # metadb -a c0t1d0s6

复制代码

Note that there appears to be a lot of confusion regarding the recommended number and location of state database replicas. According the the DiskSuite reference manual:

State database replicas contain configuration and status information of all metadevices and hot spares. Multiple copies (replicas) are maintained to provide redundancy. Multiple copies also prevent the database from being corrupted during a system crash (at most, only one copy if the database will be corrupted).

State database replicas are also used for mirror resync regions. Too few state database replicas relative to the number of mirrors may cause replica I/O to impact mirror performance.

At least three replicas are recommended. DiskSuite allows a maximum of 50 replicas. The following guidelines are recommended:

For a system with only a single drive: put all 3 replicas in one slice.

For a system with two to four drives: put two replicas on each drive.

For a system with five or more drives: put one replica on each drive.

In general, it is best to distribute state database replicas across slices, drives, and controllers, to avoid single points-of-failure.

Each state database replica occupies 517 KB (1034 disk sectors) of disk storage by default. Replicas can be stored on: a dedicated disk partition, a partition which will be part of a metadevice, or a partition which will be part of a logging - device.

Note - Replicas cannot be stored on the root (/), swap, or /usr slices, or on slices containing existing file systems or data.

Starting with DiskSuite 4.2.1, an optional /etc/system parameter exists which allows DiskSuite to boot with just 50% of the state database replicas online. For example, if one of the two boot disks were to fail, just two of the four state database replicas would be available. Without this /etc/system parameter (or with older versions of DiskSuite), the system would complain of "insufficient state database replicas", and manual intervention would be required on bootup. To enable the "50% boot" behaviour with DiskSuite 4.2.1, execute the following command:

1. # echo "set md:mirrored_root_flag=1" >;>; /etc/system

复制代码

3.Define the metadevices on c0t0d0 (/):

1. # metainit -f d10 1 1 c0t0d0s0
   
2. # metainit -f d20 1 1 c0t1d0s0
   
3. # metainit d0 -m d10

复制代码

The metaroot command edits the /etc/vfstab and /etc/system files:

1. # metaroot d0

复制代码

Define the metadevices for c0t0d0s1 (swap):

1. # metainit -f d11 1 1 c0t0d0s1
   
2. # metainit -f d21 1 1 c0t1d0s1
   
3. # metainit d1 -m d11

复制代码

Define the metadevices for c0t0d0s4 (/var):

1. # metainit -f d14 1 1 c0t0d0s4
   
2. # metainit -f d24 1 1 c0t1d0s4
   
3. # metainit d4 -m d14

复制代码

4.Edit /etc/vfstab so that it references the DiskSuite metadevices instead of simple slices:

1. #device           device          mount   FS      fsck    mount   mount
   
2. #to mount         to fsck         point   type    pass    at boot options
   
3. #
   
4. fd               -                /dev/fd fd      -       no      -
   
5. /proc            -                /proc   proc    -       no      -
   
6. /dev/md/dsk/d1   -                -       swap    -       no      -
   
7. /dev/md/dsk/d0   /dev/md/rdsk/d0  /       ufs     1       no      logging
   
8. /dev/md/dsk/d4   /dev/md/rdsk/d4  /var    ufs     1       no      logging
   
9. swap             -                /tmp    tmpfs   -       yes     -

复制代码

5.Reboot the system:

1. # lockfs -fa
   
2. 
   
3. # sync;sync;sync;init 6

复制代码

6.After the system reboots from the metadevices for /, /var, and swap, set up mirrors:

1. # metattach d0 d20
   
2. # metattach d1 d21
   
3. # metattach d4 d24

复制代码

The process of synchronizing the data to the mirror disk will take a while. You can monitor its progress via the command:

1. # metastat|grep -i progress

复制代码

7.Capture the DiskSuite configuration in the text file md.tab. With Solaris 2.6 and Solaris 7, this text file resides in the directory /etc/opt/SUNWmd; however, more recent versions of Solaris place the file in the /etc/lvm directory. We'll assume that we're running Solaris 8 here:

1. # metastat -p | tee /etc/lvm/md.tab

复制代码

8.In order for the system to be able to dump core in the event of a panic, the dump device needs to reference the DiskSuite metadevice:

1. # dumpadm -d /dev/md/dsk/d1

复制代码

9.If the primary boot disk should fail, make it easy to boot from the mirror. Some sites choose to alter the OBP "boot-device" variable; in this case, we choose to simply define the device aliases "sds-root" and "sds-mirror". In the event that the primary boot device ("disk" or "sds-root" should fail, the administrator simply needs to type "boot sds-mirror" at the OBP prompt.

Determine the device path to the boot devices for both the primary and mirror:

1. # ls -l /dev/dsk/c0t0d0s0 /dev/dsk/c0t1d0s0
   
2. lrwxrwxrwx   1 root     root          41 Oct 17 11:48 /dev/dsk/c0t0d0s0 ->; ../..
   
3. /devices/pci@1f,4000/scsi@3/sd@0,0:a
   
4. lrwxrwxrwx   1 root     root          41 Oct 17 11:48 /dev/dsk/c0t1d0s0 ->; ../..
   
5. /devices/pci@1f,4000/scsi@3/sd@1,0:a

复制代码

Use the device paths to define the sds-root and sds-mirror device aliases (note that we use the label "disk" instead of "sd" in the device alias path):

1. # eeprom "nvramrc=devalias sds-root /pci@1f,4000/scsi@3/disk@0,0
   
2. devalias sds-mirror /pci@1f,4000/scsi@3/disk@1,0"
   
3. # eeprom "use-nvramrc?=true"

复制代码

Test the process of booting from either sds-root or sds-mirror.

Once the above sequence of steps has been completed. the system will look as follows:

1. # metadb
   
2.         flags           first blk       block count
   
3.      a m  p  luo        16              1034            /dev/dsk/c0t0d0s5
   
4.      a    p  luo        16              1034            /dev/dsk/c0t0d0s6
   
5.      a    p  luo        16              1034            /dev/dsk/c0t1d0s5
   
6.      a    p  luo        16              1034            /dev/dsk/c0t1d0s6
   
7. 
   
8. # df -k
   
9. Filesystem            kbytes    used   avail capacity  Mounted on
   
10. /dev/md/dsk/d0       6607349  845208 5696068    13%    /
    
11. /proc                      0       0       0     0%    /proc
    
12. fd                         0       0       0     0%    /dev/fd
    
13. mnttab                     0       0       0     0%    /etc/mnttab
    
14. /dev/md/dsk/d4       1016863    8414  947438     1%    /var
    
15. swap                 1443840       8 1443832     1%    /var/run
    
16. swap                 1443848      16 1443832     1%    /tmp

复制代码

Trans metadevices for logging

UFS filesystem logging was first supported with Solaris 7. Prior to that release, one could create trans metadevices with DiskSuite to achieve the same effect. For Solaris 7 and up, it's much easier to simply enable ufs logging by adding the word "logging" to the last field of the /etc/vfstab file. The following section is included for those increasingly rare Solaris 2.6 installations.

The following two steps assume that you are have an available (<=64MB) slice 3 available for logging.

1.Define the trans metadevice mirror (c0t0d0s3):

1. # metainit d13 1 1 c0t0d0s3
   
2. # metainit d23 1 1 c0t1d0s3
   
3. # metainit d3 -m d13
   
4. # metattach d3 d23

复制代码

2.Make /var use the trans meta device for logging:

1. # metainit -f d64 -t d4 d3

复制代码

Edit vfstab as follows:

1. /dev/md/dsk/d64 /dev/md/rdsk/d64 /var ufs 1 no -

复制代码

Ensure that no volumes are syncing before running the following:

1. # sync;sync;sync;init 6

复制代码

东方蜘蛛

Disksuite examples

Here are some quick examples on doing a few other DiskSuite tasks:
creating a striped metadevice:

1. # metainit d10 1 2 c0t1d0s0 c0t2d0s0 -i 32k

复制代码

creating a mirror of two slices:

1. # metainit d60 1 1 c0t2d0s0
   
2. # metainit d61 1 1 c0t3d0s0
   
3. # metainit d6 -m d60
   
4. # metattach d6 d61

复制代码

creating a concatenation of 2 slices:

1. # metainit d25 2 1 c0t1d0s0 1 c0t2d0s0

复制代码

creating a concatenation of 4 slices:

1. # metainit d25 4 1 c0t1d0s0 1 c0t2d0s0 1 c0t3d0s0 1 c0t4d0s0

复制代码

creating a concatenation of 2 stripes:

1. # metainit d0 2 4 c2t0d0s6 c2t1d0s6 c2t2d0s6 c2t3d0s6 -i 64k 2 c3t0d0s6 c3t1d0s6 -i 64k

复制代码

creating a raid5 metadevice from three slices:

1. # metainit d45 -r c2t3d0s0 c3t0d0s0 c4t0d0s0

复制代码

东方蜘蛛

Replacing a failed bootdisk
In the following example, the host has a failed bootdisk (c0t0d0). Fortunately, the system is using DiskSuite, with a mirror at c0t1d0. The following sequence of steps can be used to restore the system to full redundancy.

System fails to boot

When the system attempts to boot, it fails to find a valid device as required by the boot-device path at device alias "disk". It then attempts to boot from the network:

1. screen not found.
   
2. Can't open input device.
   
3. Keyboard not present.  Using ttya for input and output.
   
4. 
   
5. Sun Ultra 30 UPA/PCI (UltraSPARC-II 296MHz), No Keyboard
   
6. OpenBoot 3.27, 512 MB memory installed, Serial #9377973.
   
7. Ethernet address 8:0:20:8f:18:b5, Host ID: 808f18b5.
   
8. 
   
9. 
   
10. 
    
11. Initializing Memory
    
12. Timeout waiting for ARP/RARP packet
    
13. Timeout waiting for ARP/RARP packet
    
14. Timeout waiting for ARP/RARP packet
    
15. ...

复制代码

Boot from mirror

At this point, the administrator realizes that the boot disk has failed, and queries the device aliases to find the one corresponding to the disksuite mirror:

1. ok devalias
   
2. sds-mirror               /pci@1f,4000/scsi@3/disk@1,0
   
3. sds-root                 /pci@1f,4000/scsi@3/disk@0,0
   
4. net                      /pci@1f,4000/network@1,1
   
5. disk                     /pci@1f,4000/scsi@3/disk@0,0
   
6. cdrom                    /pci@1f,4000/scsi@3/disk@6,0:f
   
7. ...

复制代码

The administrator then boots the system from the mirror device "sds-mirror":

1. ok boot sds-mirror

复制代码

The system starts booting off of sds-mirror. However, because there are only two of the original four state database replicas available, a quorum is not achieved. The system requires manual intervention to remove the two failed state database replicas:

Starting with DiskSuite 4.2.1, an optional /etc/system parameter exists which allows DiskSuite to boot with just 50% of the state database replicas online. For example, if one of the two boot disks were to fail, just two of the four state database replicas would be available. Without this /etc/system parameter (or with older versions of DiskSuite), the system would complain of "insufficient state database replicas", and manual intervention would be required on bootup. To enable the "50% boot" behaviour with DiskSuite 4.2.1, execute the following command:

1. # echo "set md:mirrored_root_flag=1" >;>; /etc/system

复制代码

1. Boot device: /pci@1f,4000/scsi@3/disk@1,0  File and args:
   
2. SunOS Release 5.8 Version Generic_108528-07 64-bit
   
3. Copyright 1983-2001 Sun Microsystems, Inc.  All rights reserved.
   
4. WARNING: md: d10: /dev/dsk/c0t0d0s0 needs maintenance
   
5. WARNING: forceload of misc/md_trans failed
   
6. WARNING: forceload of misc/md_raid failed
   
7. WARNING: forceload of misc/md_hotspares failed
   
8. configuring IPv4 interfaces: hme0.
   
9. Hostname: pegasus
   
10. metainit: pegasus: stale databases
    
11. 
    
12. Insufficient metadevice database replicas located.
    
13. 
    
14. Use metadb to delete databases which are broken.
    
15. Ignore any "Read-only file system" error messages.
    
16. Reboot the system when finished to reload the metadevice database.
    
17. After reboot, repair any broken database replicas which were deleted.
    
18. 
    
19. Type control-d to proceed with normal startup,
    
20. (or give root password for system maintenance): ******
    
21. 
    
22. single-user privilege assigned to /dev/console.
    
23. Entering System Maintenance Mode
    
24. 
    
25. Oct 17 19:11:29 su: 'su root' succeeded for root on /dev/console
    
26. Sun Microsystems Inc.   SunOS 5.8       Generic February 2000
    
27. 
    
28. # metadb -i
    
29.         flags           first blk       block count
    
30.     M     p             unknown         unknown         /dev/dsk/c0t0d0s5
    
31.     M     p             unknown         unknown         /dev/dsk/c0t0d0s6
    
32.      a m  p  lu         16              1034            /dev/dsk/c0t1d0s5
    
33.      a    p  l          16              1034            /dev/dsk/c0t1d0s6
    
34. o - replica active prior to last mddb configuration change
    
35. u - replica is up to date
    
36. l - locator for this replica was read successfully
    
37. c - replica's location was in /etc/lvm/mddb.cf
    
38. p - replica's location was patched in kernel
    
39. m - replica is master, this is replica selected as input
    
40. W - replica has device write errors
    
41. a - replica is active, commits are occurring to this replica
    
42. M - replica had problem with master blocks
    
43. D - replica had problem with data blocks
    
44. F - replica had format problems
    
45. S - replica is too small to hold current data base
    
46. R - replica had device read errors
    
47. 
    
48. 
    
49. # metadb -d c0t0d0s5 c0t0d0s6
    
50. metadb: pegasus: /etc/lvm/mddb.cf.new: Read-only file system
    
51. 
    
52. # metadb -i
    
53.         flags           first blk       block count
    
54.      a m  p  lu         16              1034            /dev/dsk/c0t1d0s5
    
55.      a    p  l          16              1034            /dev/dsk/c0t1d0s6
    
56. o - replica active prior to last mddb configuration change
    
57. u - replica is up to date
    
58. l - locator for this replica was read successfully
    
59. c - replica's location was in /etc/lvm/mddb.cf
    
60. p - replica's location was patched in kernel
    
61. m - replica is master, this is replica selected as input
    
62. W - replica has device write errors
    
63. a - replica is active, commits are occurring to this replica
    
64. M - replica had problem with master blocks
    
65. D - replica had problem with data blocks
    
66. F - replica had format problems
    
67. S - replica is too small to hold current data base
    
68. R - replica had device read errors
    
69. 
    
70. # reboot -- sds-mirror

复制代码

Check extent of failures

Once the reboot is complete, the administrator then logs into the system and checks the status of the DiskSuite metadevices. Not only have the state database replicas failed, but all of the DiskSuite metadevices previously located on device c0t0d0 need to be replaced. Clearly the disk has completely failed.

1. pegasus console login: root
   
2. Password:  ******
   
3. Oct 17 19:14:03 pegasus login: ROOT LOGIN /dev/console
   
4. Last login: Thu Oct 17 19:02:42 from rambler.wakefie
   
5. Sun Microsystems Inc.   SunOS 5.8       Generic February 2000
   
6. 
   
7. # metastat
   
8. d0: Mirror
   
9.     Submirror 0: d10
   
10.       State: Needs maintenance
    
11.     Submirror 1: d20
    
12.       State: Okay         
    
13.     Pass: 1
    
14.     Read option: roundrobin (default)
    
15.     Write option: parallel (default)
    
16.     Size: 13423200 blocks
    
17. 
    
18. d10: Submirror of d0
    
19.     State: Needs maintenance
    
20.     Invoke: metareplace d0 c0t0d0s0 <new device>;
    
21.     Size: 13423200 blocks
    
22.     Stripe 0:
    
23.         Device              Start Block  Dbase State        Hot Spare
    
24.         c0t0d0s0                   0     No    Maintenance  
    
25. 
    
26. 
    
27. d20: Submirror of d0
    
28.     State: Okay         
    
29.     Size: 13423200 blocks
    
30.     Stripe 0:
    
31.         Device              Start Block  Dbase State        Hot Spare
    
32.         c0t1d0s0                   0     No    Okay         
    
33. 
    
34. 
    
35. d1: Mirror
    
36.     Submirror 0: d11
    
37.       State: Needs maintenance
    
38.     Submirror 1: d21
    
39.       State: Okay         
    
40.     Pass: 1
    
41.     Read option: roundrobin (default)
    
42.     Write option: parallel (default)
    
43.     Size: 2100000 blocks
    
44. 
    
45. d11: Submirror of d1
    
46.     State: Needs maintenance
    
47.     Invoke: metareplace d1 c0t0d0s1 <new device>;
    
48.     Size: 2100000 blocks
    
49.     Stripe 0:
    
50.         Device              Start Block  Dbase State        Hot Spare
    
51.         c0t0d0s1                   0     No    Maintenance  
    
52. 
    
53. 
    
54. d21: Submirror of d1
    
55.     State: Okay         
    
56.     Size: 2100000 blocks
    
57.     Stripe 0:
    
58.         Device              Start Block  Dbase State        Hot Spare
    
59.         c0t1d0s1                   0     No    Okay         
    
60. 
    
61. 
    
62. d4: Mirror
    
63.     Submirror 0: d14
    
64.       State: Needs maintenance
    
65.     Submirror 1: d24
    
66.       State: Okay         
    
67.     Pass: 1
    
68.     Read option: roundrobin (default)
    
69.     Write option: parallel (default)
    
70.     Size: 2100000 blocks
    
71. 
    
72. d14: Submirror of d4
    
73.     State: Needs maintenance
    
74.     Invoke: metareplace d4 c0t0d0s4 <new device>;
    
75.     Size: 2100000 blocks
    
76.     Stripe 0:
    
77.         Device              Start Block  Dbase State        Hot Spare
    
78.         c0t0d0s4                   0     No    Maintenance  
    
79. 
    
80. 
    
81. d24: Submirror of d4
    
82.     State: Okay         
    
83.     Size: 2100000 blocks
    
84.     Stripe 0:
    
85.         Device              Start Block  Dbase State        Hot Spare
    
86.         c0t1d0s4                   0     No    Okay         

复制代码

Replace failed disk and restore redundancy

The administrator replaces the failed disk with a new disk of the same geometry. Depending on the system model, the disk replacement may require that the system be powered down. The replacement disk is then partitioned identically to the mirror, and state database replicas are copied onto the replacement disk. Finally, the metareplace command copies that data from the mirror to the replacement disk, restoring redundancy to the system.

1. # prtvtoc /dev/rdsk/c0t1d0s2 | fmthard -s - /dev/rdsk/c0t0d0s2
   
2. fmthard:  New volume table of contents now in place.
   
3. 
   
4. # installboot /usr/platform/sun4u/lib/fs/ufs/bootblk /dev/rdsk/c0t0d0s0
   
5. 
   
6. # metadb -f -a /dev/dsk/c0t0d0s5
   
7. 
   
8. # metadb -f -a /dev/dsk/c0t0d0s6
   
9. 
   
10. # metadb -i
    
11.         flags           first blk       block count
    
12.      a        u         16              1034            /dev/dsk/c0t0d0s5
    
13.      a        u         16              1034            /dev/dsk/c0t0d0s6
    
14.      a m  p  luo        16              1034            /dev/dsk/c0t1d0s5
    
15.      a    p  luo        16              1034            /dev/dsk/c0t1d0s6
    
16. o - replica active prior to last mddb configuration change
    
17. u - replica is up to date
    
18. l - locator for this replica was read successfully
    
19. c - replica's location was in /etc/lvm/mddb.cf
    
20. p - replica's location was patched in kernel
    
21. m - replica is master, this is replica selected as input
    
22. W - replica has device write errors
    
23. a - replica is active, commits are occurring to this replica
    
24. M - replica had problem with master blocks
    
25. D - replica had problem with data blocks
    
26. F - replica had format problems
    
27. S - replica is too small to hold current data base
    
28. R - replica had device read errors
    
29. 
    
30. # metareplace -e d0 c0t0d0s0
    
31. d0: device c0t0d0s0 is enabled
    
32. 
    
33. # metareplace -e d1 c0t0d0s1
    
34. d1: device c0t0d0s1 is enabled
    
35. 
    
36. # metareplace -e d4 c0t0d0s4
    
37. d4: device c0t0d0s4 is enabled

复制代码

Once the resync process is complete, operating system redundancy has been restored.

ammy

收了先     

solaris小兵

强烈支持！！
顶！！

东方蜘蛛

Performing maintenance when booted from cdrom

Introduction
If the system has to be booted from a cdrom or from the network ("boot cdrom" or "boot net" in order to perform maintenance, the operator needs to adjust for the existence of a mirrored operating system. Because these alternate boot devices do not include the drivers necessary for disksuite, they cannot be used to operate on state database replicas and Disksuite metadevices. This raises subtle issues addressed below.

Typically, the administrator is often under pressure while performing these types of maintenance. Because simple mistakes at this stage can render the system unusable, it is important that the process be well documented and tested prior to using it in production. Fortunately, this process is simpler than that for Veritas volume manager because there are no "de-encapsulation" issues to address.

Booting from cdrom with DiskSuite mirrored devices

In the example below, the server pegasus has two internal disks (c0t0d0 and c0t1d0) under Disksuite control. The operating system is mirrored between the two devices, with slices five and six on each disk employed for state database replicas. Assume that the administrator has forgotten the root password on this server, and needs to boot from cdrom in order to edit the shadow file.

1.Insert the Solaris operating system CD into the cdrom drive and boot from it into single-user mode:

1. ok boot cdrom -s
   
2. 
   
3. Initializing Memory
   
4. Rebooting with command: boot cdrom -s
   
5. Boot device: /pci@1f,4000/scsi@3/disk@6,0:f  File and args: -s
   
6. SunOS Release 5.8 Version Generic_108528-07 64-bit
   
7. Copyright 1983-2001 Sun Microsystems, Inc.  All rights reserved.
   
8. Configuring /dev and /devices
   
9. Using RPC Bootparams for network configuration information.
   
10. Skipping interface hme0
    
11. 
    
12. INIT: SINGLE USER MODE
    
13. #

复制代码

2.Fsck and mount the root disk's "/" partition in order to edit the /etc/shadow file:

1. # fsck -y /dev/rdsk/c0t0d0s0
   
2. 
   
3. # mount /dev/dsk/c0t0d0s0 /a

复制代码

3.Remove the encrypted password from the /a/etc/shadow file:

1. # TERM=vt100; export TERM
   
2. 
   
3. # vi /a/etc/shadow

复制代码

For example, if the entry for the root user looks like the following:

1. root:NqfAn3tWOy2Ro:6445::::::

复制代码

Change it so that is looks as follows:

1. root::6445::::::

复制代码

4.Comment out the rootdev entry from the /a/etc/system file:

1. # vi /a/etc/system

复制代码

For example, change the line:

1. rootdev:/pseudo/md@0:0,0,blk

复制代码

to

1. * rootdev:/pseudo/md@0:0,0,blk

复制代码

5.Update the /a/etc/vfstab file so that it references simple disk slices instead of disksuite metadevices. Note that you only have to change those enties that correspond to operating system slices.

For example, one would change the following /a/etc/vfstab file:

1. #device             device             mount   FS      fsck    mount   mount
   
2. #to mount           to fsck            point   type    pass    at boot options
   
3. #
   
4. fd                  -                  /dev/fd fd      -       no      -
   
5. /proc               -                  /proc   proc    -       no      -
   
6. /dev/md/dsk/d1      -                  -       swap    -       no      -
   
7. /dev/md/dsk/d0      /dev/md/rdsk/d0    /       ufs     1       no      logging
   
8. /dev/md/dsk/d4      /dev/md/rdsk/d4    /var    ufs     1       no      logging
   
9. swap                -                  /tmp    tmpfs   -       yes     -

复制代码

to:

1. #device             device             mount   FS      fsck    mount   mount
   
2. #to mount           to fsck            point   type    pass    at boot options
   
3. #
   
4. fd                  -                  /dev/fd fd      -       no      -
   
5. /proc               -                  /proc   proc    -       no      -
   
6. /dev/dsk/c0t0d0s1   -                  -       swap    -       no      -
   
7. /dev/dsk/c0t0d0s0   /dev/rdsk/c0t0d0s0 /       ufs     1       no      logging
   
8. /dev/dsk/c0t0d0s4   /dev/rdsk/c0t0d0s4 /var    ufs     1       no      logging
   
9. swap                -                  /tmp    tmpfs   -       yes     -

复制代码

6.Unmount the root filesystem, fsck it, and return to the ok prompt:

1. # cd /; umount /a; fsck -y /dev/rdsk/c0t0d0s0
   
2. 
   
3. # stop-a
   
4. ok

复制代码

7.Boot from c0t0d0 into single user mode. It is important to boot just to single user mode so that DiskSuite does not start automatically:

1. ok boot -sw

复制代码

8.When prompted for the root password, just press the ENTER key. Once at the shell prompt, clear the metadevices that referenced the filesystems that you updated in the /a/etc/vfstab file above:

1. # metaclear -f -r d0 d1 d4

复制代码

Now would be an appropriate time to create a new password for the root account, via the passwd root command

9.Exit from single user mode and continue the boot process.

1. # exit

复制代码

IT业的民工

好贴！

ga0feng

强贴留名

lyh003473

这个帖子很不错