Sponsored Content
Operating Systems Solaris Replacing a failed disk using SVM Post 302993834 by fretagi on Wednesday 15th of March 2017 01:12:38 AM
Old 03-15-2017
for dumpadm:
Code:
root@mhcominf01:/# dumpadm
      Dump content: kernel pages
       Dump device: /dev/md/dsk/d30 (dedicated)
Savecore directory: /var/crash/mhcominf01
  Savecore enabled: yes
   Save compressed: on

for swap -l
Code:
root@mhcominf01:/# swap -l
swapfile             dev  swaplo blocks   free
/dev/md/dsk/d20     85,20      8 20980880 20980880
root@mhcominf01:/#

when running metastat, I come across the following:
Code:
d32: Submirror of d30
    State: Needs maintenance
    Invoke: metareplace d30 c0t2d0s3 <new device>
    Size: 459940950 blocks (219 GB)
    Stripe 0:
        Device     Start Block  Dbase        State Reloc Hot Spare
        c0t2d0s3          0     No     Maintenance   Yes

,
and:

Code:
d22: Submirror of d20
    State: Needs maintenance
    Invoke: metareplace d20 c0t2d0s1 <new device>
    Size: 20980890 blocks (10 GB)
    Stripe 0:
        Device     Start Block  Dbase        State Reloc Hot Spare
        c0t2d0s1          0     No     Maintenance   Yes

these are two different stattements. What do they mean, what is the impact on the system?
Please explain
 

10 More Discussions You Might Find Interesting

1. Solaris

Disk replacement with svm

I dont even know what raid level this is, but its raid 5 mirrored from the looks of it. I have a failed disk (t12) within this mirror. What is the best way to replace this disk? 2 things concern me, isn't there a command to prepare the disk for a hot swap? and what should i do with the... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies

2. Solaris

Disk Replacement SVM

Hello, Can someone advise the proper procedure for replacing a mirrored disk in SVM. I have checked the docs and various websites but the procedure seems to vary. This is what I would do... 1. Remove the db replicas from the bad disk. 2. Detach it from the mirror 3. Clear it with... (4 Replies)
Discussion started by: Actuator
4 Replies

3. Solaris

Removing Disk from SVM

Hi All, I have to remove the disk from SVM. Kindly guide me or suggest me some link where in I can steps to remove SVM from Solaris 10 .Also I have one metaset which require deletion. Thanks in anticipation! (10 Replies)
Discussion started by: kumarmani
10 Replies

4. Solaris

mirroring root disk using svm - but no free slices for metadb's

Hi all, we have an existing system that was configured using just one of the (two) internal disks. I want to mirror the disk using SVM, but have realised there is no free slice for creating the metadb's. Is there a workaround I can use for this? In the past we have always kept slice 7 free -... (8 Replies)
Discussion started by: badoshi
8 Replies

5. Solaris

Disk space missing under SVM

Hi Gurus, I've got an issue here: (1) Hardware: Sun NetraT1, (2) OS: Solaris 10, (3) SVM metastat shows /var having 12 GB. df shows /var having 4 GB. Real space for /var is about 4 GB since I can't move a big file to it. How is 8 GB space missing? Does /var/run swap need to account? Can I... (5 Replies)
Discussion started by: aixlover
5 Replies

6. Solaris

Command to find the failed disks in SVM and VxVM

How to find & replace bad disks in solaris & VXVM?plz explain step by step? (2 Replies)
Discussion started by: xtreams
2 Replies

7. Solaris

Root Disk mirroring in SVM

Dear All, Please help me to configure root mirroring using SVM in Solaris 9. Thanks and Regards, Lakkireddy BR (3 Replies)
Discussion started by: lbreddy
3 Replies

8. Solaris

Replacing a hard disk (SVM) with a soft partition?

The following is the summarry:- 1) Four disks in server ie (c1t0d0. c1t1d0, c1t2d0, c1t3d0). c1t2d0 is the disk to be replaced. c1t0d0 and c1t2d0 are mirrors. c1t1d0 and c1t3d0 are mirrors. Metadb to be deleted is in c1t2d0s7 a) Mirror d35 has 2 submirrors d38 and d39 d38 is a stripe... (0 Replies)
Discussion started by: aji1729
0 Replies

9. Solaris

Root disk mirroring in SVM

I tried doing rootdisk mirroring in my local host , i added a new Ide disk in my system and copied the prtvtoc from root disk to the newly added disk, and then when i tried to add database replicas on both the disks, it was added for boot disk but for the newly added disk i gave the error, which... (6 Replies)
Discussion started by: Laxxi
6 Replies

10. Solaris

Replacing a Disk in a ODS/SVM Mirror

Hi All BAsed on the below I would like to verifu two things (1) The udnerlying mirroris for '/mnt' na dit onlcy contaisne 1 sub-mirror, with one sliceon is one disk and hence, data loss on the mount point (the mount point, '/mnt' is backed up) (2) the Procedure for renewal # df -kh /mnt... (2 Replies)
Discussion started by: stevie_velvet
2 Replies
metastat(1M)						  System Administration Commands					      metastat(1M)

NAME
metastat - display status for metadevice or hot spare pool SYNOPSIS
/usr/sbin/metastat -h /usr/sbin/metastat [-a] [-B] [-D] [-c] [-i] [-p] [-q] [-s setname] [-t] [metadevice...] [hot_spare_pool...] /usr/sbin/metastat [-a] [-B] [-D] [-c] [-i] [-p] [-q] [-s setname] component... DESCRIPTION
The metastat command displays the current status for each metadevice (including stripes, concatenations, concatenations of stripes, mir- rors, RAID5, soft partitions, and trans devices) or hot spare pool, or of specified metadevices, components, or hot spare pools. It is helpful to run the metastat command after using the metattach command to view the status of the metadevice. metastat displays the state of each Solaris Volume Manager RAID-1 volume on the system. The possible states include: Okay The device reports no errors. Needs maintenance A problem has been detected. This requires that the system administrator replace the failed physical device. Volumes displaying Needs maintenance have incurred no data loss, although additional failures could risk data loss. Take action as quickly as possible. Last erred A problem has been detected. Data loss is a possibility. This might occur if a component of a submirror fails and is not replaced by a hot spare, therefore going into Needs maintenance state. If the corresponding component also fails, it would go into Last erred state and, as there is no remaining valid data source, data loss could be a possibility. Unavailable A device cannot be accessed, but has not incurred errors. This might occur if a physical device has been removed with Solaris Dynamic Reconfiguration (DR) features, thus leaving the Solaris Volume Manager volume unavailable. It could also occur if an array or disk is powered off at system initialization, or if a >1TB volume is present when the system is booted in 32-bit mode. After the storage has been made available, run the metastat command with the -i option to update the status of the metadevices. This clears the unavailable state for accessible devices. See the for instructions on replacing disks and handling volumes in Needs maintenance or Last erred states. OPTIONS
The following options are supported: -a Display all disk sets. Only metadevices in disk sets that are owned by the current host are displayed. -B Display the current status of all of the 64-bit metadevices and hot spares. -c Display concise output. There is one line of output for each metadevice. The output shows the basic structure and the error status, if any, for each metadevice. The -c output format is distinct from the -p output format. The -p option does not display metadevice status and is not intended as human-readable output. -D Display the current status of all of the descriptive name metadevices and hotspares. -h Display usage message. -i Check the status of RAID-1 (mirror) volumes, RAID-5 volumes, and hot spares. The inquiry checks each metadevice for accessi- bility, starting at the top level metadevice. When problems are discovered, the metadevice state databases are updated as if an error had occurred. -p Display the list of active metadevices and hot spare pools in the same format as md.tab. See md.tab(4). The -p output is designed for snapshotting the configuration for later recovery or setup. -q Display the status for metadevices without the device relocation information. -s setname Specify the name of the disk set on which metastat works. Using the -s option causes the command to perform its administra- tive function within the specified disk set. Without this option, the command performs its function on metadevices and hot spare pools in the local disk set. -t Display the current status and timestamp for the specified metadevices and hot spare pools. The timestamp provides the date and time of the last state change. OPERANDS
The following operands are supported: component Display the status of the component hosting a soft partition, including extents, starting blocks, and block count. hot_spare_pool Display the status of the specified hot spare pool(s). metadevice Display the status of the specified metadevice(s). If a trans metadevice is specified, the status of the master and log devices is also displayed. Trans metadevices have been replaced by UFS logging. See NOTES. EXAMPLES
Example 1 Output Showing Mirror with Two Submirrors The following example shows the partial output of the metastat command after creating a mirror, opt_mirror, consisting of two submirrors, opt_sub1 and opt_sub2. # metastat opt_mirror opt_mirror: Mirror Submirror 0: opt_sub1 State: Okay Submirror 1: opt_sub2 State: Resyncing Resync in progress: 15 % done Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 2006130 blocks . . . Example 2 Soft Partition on Mirror with Submirror The following example shows the partial output of the metastat command after creating a soft partition, d3, on concat d2, which is built on a soft partition. # metastat d2: Concat/Stripe Size: 204800 blocks Stripe 0: Device Start Block Dbase State Hot Spare d0 0 No Okay d0: Soft Partition Component: c0t3d0s0 Status: Okay Size: 204800 blocks Extent Start Block Block count 0 129 204800 d3: Soft Partition Component: d2 Status: Okay Size: 202752 blocks Extent Start Block Block count 0 129 202752 Example 3 Trans Metadevice The following example shows the output of the metastat command after creating a trans metadevice. # metastat d2: Concat/Stripe Size: 204800 blocks Stripe 0: Device Start Block Dbase State Hot Spare d0 0 No Okay d0: Soft Partition Component: c0t3d0s0 Status: Okay Size: 204800 blocks Extent Start Block Block count 0 129 204800 d3: Soft Partition Component: d2 Status: Okay Size: 202752 blocks Extent Start Block Block count 0 129 202752 Example 4 Multi-owner disk set The following example shows the output of the metastat command with a multi-owner disk set and application-based mirror resynchronization option. Application-based resynchronization is set automatically if needed. # metastat -s oban oban/d100: Mirror Submirror 0: oban/d10 State: Okay Submirror 1: oban/d11 State: Okay Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Resync option: application based Owner: None Size: 1027216 blocks (501 MB) oban/d10: Submirror of oban/d100 State: Okay Size: 1027216 blocks (501 MB) Stripe 0: Device Start Block Dbase State Reloc Hot Spare c1t3d0s0 0 No Okay oban/d11: Submirror of oban/d100 State: Okay Size: 1027216 blocks (501 MB) Stripe 0: Device Start Block Dbase State Reloc Hot Spare c1t4d0s0 0 No Okay WARNINGS
metastat displays states as of the time the command is entered. It is unwise to use the output of the metastat -p command to create a md.tab(4) file for a number of reasons: o The output of metastat -p might show hot spares being used. o It might show mirrors with multiple submirrors. See metainit(1M) for instructions for creating multi-way mirrors using metainit and metattach. o A slice may go into an error state after metastat -p is issued. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWmdr | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ SEE ALSO
mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M), metarecover(1M), metarename(1M), metareplace(1M), metaroot(1M), metaset(1M), metassist(1M), metasync(1M), metattach(1M), md.tab(4), md.cf(4), mddb.cf(4), md.tab(4), attributes(5), md(7D) NOTES
Trans metadevices have been replaced by UFS logging. Existing trans devices are not logging--they pass data directly through to the under- lying device. See mount_ufs(1M) for more information about UFS logging. SunOS 5.11 26 Mar 2006 metastat(1M)
All times are GMT -4. The time now is 11:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy