10 More Discussions You Might Find Interesting
1. Solaris
Hi,
We have a Solaris 10 machine with update 11 and was configured with IBM storage. It was assigned 2 LUNs (each 70GB) which were striped to make it 140GB. we have taken full backup of entire machine and Our storage team replaced IBM storage with Nimble storage (they did storage-level... (6 Replies)
Discussion started by: prvnrk
6 Replies
2. Solaris
Dear,
Required an script such that :
If metastat |grep Needs , results in some output then this command to be executed for the same :
opcmsg object=metastat a=OS msg_grp=OpC severity=critical msg_text="Need maintenance for the system $line"
With regards,
Mjoshi (3 Replies)
Discussion started by: mjoshi87
3 Replies
3. Shell Programming and Scripting
Hi,
after issuing metastat command I am getting output as follows
Actually these soft partitions are more than 100.
I want output as Device Name & Size.
for eg d4004 2.0 GB (4 Replies)
Discussion started by: tuxian
4 Replies
4. Solaris
Greetings
How can i restore metastat db after a solaris upgrade (9 to 10)?
will it work if i save and restore /etc/vfstab and /etc/lvm/md.cf file?
root@netad# metastat
d35: Mirror
Submirror 0: d38
State: Okay
Submirror 1: d39
State: Okay
Pass:... (2 Replies)
Discussion started by: kashif_islam
2 Replies
5. Solaris
Hi friends,
I'm newbie to SVM.
Just wanna try installed it on one of our server (to do mirroring for disk0 and disk1) but i think im lost until now. :(
the steps i've taken is as below:-
1.prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t1d0s2
2.metadb -a -c 3 -f c1t0d0s7... (3 Replies)
Discussion started by: kronenose
3 Replies
6. Solaris
Hi All,
Sorry to post a problem for my first post but I'm in a bit of a pickle at the minute!
I have an Ultra45 connected to a Storedge 3100 series, 2 internal, 2 external disks with a db application running on the external disks.
Now everything is working fine and we've had no downtime or... (4 Replies)
Discussion started by: TheSteed
4 Replies
7. Solaris
Hi people,
I have on problem when execute the command METASTAT...
d60: Soft Partition
Device: d10
State: Errored
Size: 12582912 blocks (6.0 GB)
Someone help me?
Thank you very much (4 Replies)
Discussion started by: denisgomes
4 Replies
8. Filesystems, Disks and Memory
I have to rescue the volumes in a soloris 7 machine. The metastat returns the following result:
d6 is dying with iostat -nE returns Harderror 3, Transports error 9
Can some offer me some help? Thank you very much. (6 Replies)
Discussion started by: nickychung
6 Replies
9. Solaris
My company is running a solaris 2.7 machine. The machine is getting slow recently. I have no expert in solaris. Please help.
I checked the log in /var/adm/message:
I also checked with the command iostat -nE. It returns:
Metastat returns the followings:
What should i do now?... (10 Replies)
Discussion started by: nickychung
10 Replies
10. Solaris
hi all,
can someone pls pass on your suggestion?
Firs thing I am testing a script which checks for the pattern 'Needs Maintenance' from metastat output and prints some messages in the screen. So i need to simulate an error in mirrored disk for metastat to give this message 'Needs Maintenance'.... (3 Replies)
Discussion started by: srirammad007
3 Replies
metastat(1M) metastat(1M)
NAME
metastat - display status for metadevice or hot spare pool
SYNOPSIS
/usr/sbin/metastat -h
/usr/sbin/metastat [-a] [-B] [-c] [-i] [-p] [-q] [-s setname] [-t] [metadevice...] [hot_spare_pool...]
/usr/sbin/metastat [-a] [-B] [-c] [-i] [-p] [-q] [-s setname] component...
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. Vol-
umes 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 pos-
sibility.
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.
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.
-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
accessibility, 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
administrative 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.
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.
Example 1: Output Showing Mirror with Two Submirrors
The following example shows the partial output of the metastat command after creating a mirror, d0, consisting of two submirrors, d70 and
d80.
# metastat d0
d0: Mirror
Submirror 0: d80
State: Okay
Submirror 1: d70
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.
The following exit values are returned:
0 Successful completion.
>0 An error occurred.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWmdr |
+-----------------------------+-----------------------------+
|Stability |Evolving |
+-----------------------------+-----------------------------+
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)
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.
30 Mar 2005 metastat(1M)