Page 90
Troubleshooting | CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems |
Fixing “needs maintenance” messages | 84 |
| |
Fixing “needs maintenance” messages
On rare occasions mirrors may get severely out of sync. An extreme example is when a disk is removed from a powered system without first being detached with a metadetach command. The situation is indicated by the appearance of a Needs maintenance message in a State line of a metastat response. For example:
#metastat d13: Mirror
Submirror 0: d11
State: Needs maintenance Submirror 1: d12
State: Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 2209680 blocks
d11: Submirror of d13
State: Needs maintenance | | |
Invoke: metareplace d13 | c0t0d0s0 |
Size: 2209680 blocks | | |
Stripe 0: | | | |
Device | Start Block | Dbase State Hot Spare |
c0t0d0s0 | 0 | No | Okay |
. | . | . | | |
#
In such situations the metareplace command can force the recovery of the failed slice. The Invoke line of the metastat response leads the way. Given the response above, for example, you would enter the following:
#metareplace -e d13 c0t0d0s0
#metastat
d13: Mirror
Submirror 0: d11
State: Resyncing
Submirror 1: d12
State: Needs maintenance
. . .
#
Contents
CentreVu Call Management System
Comments
Table of Contents
CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Index
CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems Iii
CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Disk mirroring defined
Metadevices
Backed up just as often as unmirrored systems
Concatenated
Mirrors
State databases
Solstice DiskSuite
How CMS implements disk mirroring
D19
D21 D20
D15
D11
D13 D12
D17 D16
Root filesystem Cms filesystem
Mirror layouts
Mirror d13 Mirror d21 Mirror d17
Submirror Disks
Enterprise
Required software
Additional references
How CMS implements disk mirroring
How to upgrade an Enterprise platform to disk mirroring
Disk drive slots
Increasing system capacity
Identify mirror devices
Device Names
Submirror d15 Submirror d16
System
Do this step only if you have an Enterprise 3500 system
# ls -l /dev/dsk/c1t6d0s0
How to upgrade an Enterprise platform to disk mirroring
Do this step only if you have an Enterprise 3000 system
Ok boot -r
# ls -l /dev/dsk/c2t6d0s0
Enter format partition
Flag
3500
Disk Part
Starting
# metadb -a -c3 -f /dev/rdsk/device
Enter partition q
# export PATH=$PATH/usr/opt/SUNWmd/sbin/olds
# metadb
Dx y 1 device
# metainit -f d13 D13 Concat/stripe is set up
Set up the mirrors for the root file system
# metainit -f d11 D11 Concat/stripe is set up
# metainit -f d12 D12 Concat/stripe is set up
Password password
# metaroot d13
# /usr/sbin/shutdown -i6 -g0 -y
# metainit d17 D17 Concat/stripe is set up
Set up the mirrors for the swap space
# metainit -f d15 D15 Concat/stripe is set up
# metainit d16 D16 Concat/stripe is set up
# swap -a /dev/md/dsk/d17
Set up the /cms mirror
Verify disk space
Disk Space Verification
Create an alternate boot device
# ls -l /dev/rdsk/newbootdev
# /usr/sbin/shutdown -y -i0 -g0
Ok nvalias bootdevice2 device
Ok boot bootdevice2
Sbus@3,0/SUNW,fas@3,8800000/sd@2,0
Factory installation procedures for disk mirroring
Install the hardware
Install the application software
3500 Disk Part
Check the disk.type file
# stty erase Ctrl-H # ksh -o
# olds -mirrored -mkfiles
Run the setup scripts
Ok boot -r Hostname console login root Password password
14376992 14446400
14171072 14205776
14309888
14550512
Disk Space Verification
Install the CMS software
Enter the following command ok devalias
# chmod +x /olds/chkDisks
Factory installation procedures for disk mirroring
Using the alternate boot device
Ok setenv boot-device disk # eeprom boot-device=disk
Activating chkDisks Verifying chkDisks
Canceling chkDisks
Maintaining the chkDisks crontab
# crontab -l
Print the vfstab file
Doing a Cmsadm backup on a mirrored system
Run the backup
# lp /etc/vfstab
Label and store the tapes
Restoring from a Cmsadm Backup
# cpio -icmudv -C 10240 -I device
Restoring from a Cmsadm Backup
Repairing or rebuilding the /cms file system
Repairing /cms
# umount /cms
Rebuilding /cms
If you altered the vfstab file earlier , do the following
If you did not alter the vfstab file, do the following
# metadetach d21 d20 D21 submirror d20 is detached
# metainit d19 D19 Concat/Stripe is set up
# metainit d21 mirror is set up
# metaclear d20 D20 Concat/Stripe is cleared
# newfs Dev/md/rdsk/d21
14585216 14654624
14724032 14793440
Restoring a mirrored system from a Cmsadm backup
Power off the system
Ok boot cdrom
Task Action Result
Select Language
Confirm Information
Identify the system
Continue
Click Continue
Set the Name Service options
255.255.255.0 is
Geographic Region
Installation Initial
Set the date and time
Region
Allocate Client
Installation screen is
Services? screen is
Select Languages
Select the hard disks
GB Disk
Slice Name
Click Begin Installation Reboot/No Reboot
Click Reboot
Click Continue Mount Remote File
Complete the OS installation
# /olds/olds -cleanup
Reestablish the disk mirrors
# PATH=$PATH/usr/opt/SUNWmd/sbin/olds # export Path
# olds mirrored -mkfiles Success, creating md.tab.new
# olds -mirrored -checkdisk Success, checking md.tab.new
Hostname login root Password root password
Restoring specific files from a Cmsadm backup
Adding new disks to a standard mirrored system
# /usr/opt/SUNWmd/sbin/metastat
# olds -mirrored -mkfiles c0t10d0 c0t11d0
# olds -mirrored -setup newdisk1 newdisk2
Adding new disks to a nonstandard mirrored system
# df -k /cms
# metattach d19 newdisk1 # metattach d20 newdisk2
# metattach d19 c0t10d0s1 # metattach d20 c0t11d0s1
# growfs -M /cms /dev/md/rdsk/d21
# metastat
Replacing a faulty disk
Identify the faulty disk
# ls -l /dev/dsk/c Lrwxrwxrwx 1 root Root
Dbase State Hot Spare C0t2d0s1 Okay Stripe Device
Identify the submirrors
Size 14960160 blocks Stripe Device
Dbase State Hot Spare C0t4d0s3 Okay
Detach the submirrors
Metadetach metamirror submirror
Remove state database replicas boot disks only
Replace the faulty disk drive
Recreate the state database replicas
# metainit d20
Reboot the system boot disks only
You may delay this step until a more convenient time
# metattach d21 d20
# metadb -d -f /dev/dsk/c0t0d0s1
Setting up replicas Replacing replicas
State Database Replicas
# metadb -d -c4 -f /dev/dsk/c0t0d0s1
Partitioning disks with the format command
Enter # format
FC-AL E
Enter partition q
How to tell whether your mirrored system is standard
Root Metadevice Device Names
Valid vfstab file for a non mirrored R3V8 CMS system
Examples of valid system files
Valid vfstab files
Valid vstab file for an R3V8 CMS system with mirrored disks
Valid md.tab files
Valid md.tab file for a 3 disk non mirrored R3V8 CMS system
Valid md.tab file for a 4 disk mirrored R3V8 CMS system
Excessively long resync
Unmount /cms umount /cms
Enter mount /cms Remounts /cms
If you receive a This command may hang the system
Enter setenv auto-boot? false
System fails to recognize all disk drives
Ok setenv auto-boot? true
Ok boot -r Console login root Password
Toshiba XMS5701TASUN12XCD099704/09/97
Fixing needs maintenance messages
C0t0d0s0 Okay
Boot problems
Primary boot device is not available
Ok setenv boot-device bootdevice2
Excessive reboot time
Touch /etc/notrouter
# ls /olds/chkDisks
Log files
File Name Description
# /olds/chkDisks
Message Explanation Response
Error messages
Error Messages Explanation Response
# metareplace -e d13 c0t0d0s0
Device devicename will not be used
Device devicename cannot be setup or does Not exist
Disk diskname already setup, exiting
Message Explanation
Message Response
Metadb hostname cxtyd0sz has a Metadevice database replica
No disks found! Internal error
Command not found
Metadetach systemname d21 resync Progress
Message
Error Messages Response
Disk is not recognized by cms
DiskSuite Software must be installed To run this script
File filename could not be restored
/cms filesystem needs to be mounted
Enter reset-all
Unbalanced configurations not supported
Touch /cms/db/unixstart cannot create
Configuration, configure manually
You must be root in order to run this command
Usage olds -mirrored -checkdisks
Symbols
Index
Needs maintenance messages
How Are We Doing?