Sponsored Content
Operating Systems Solaris SVM metastat -- needs maintenance Post 97140 by dangral on Thursday 26th of January 2006 02:50:19 PM
Old 01-26-2006
I dont see anything strange in that output:
Quote:
iostat -En
c0t6d0 Soft Errors: 1 Hard Errors: 0 Transport Errors: 0
Vendor: TOSHIBA Product: DVD-ROM SD-M1711 Revision: 1005 Serial No:
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0
c1t1d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: SEAGATE Product: ST373307FSUN72G Revision: 0307 Serial No: 0334B1RPX4
Size: 73.40GB <73400057856 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
c1t0d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: SEAGATE Product: ST373307FSUN72G Revision: 0307 Serial No: 0334B1S42R
Size: 73.40GB <73400057856 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
Also, my root mirror is complaining. It's posted in the original post. Anyhow, how can I be sure that 1) its a disk failure 2) which disk I need to replace.
 

10 More Discussions You Might Find Interesting

1. Solaris

Help on metastat

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

2. Solaris

SVM - metastat - Last Erred

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

3. Filesystems, Disks and Memory

What should I do with this metastat result? metareplace everything?

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

4. Solaris

Softpartition State: Errored in Command MetaStat

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

5. Solaris

Metastat shows "maintenance" and "last-erred"

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

6. Solaris

SVM Solaris 8 Problem. Metastat output looping

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

7. Solaris

restore metastat configuration after solaris upgrade

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

8. Shell Programming and Scripting

Grep contents from metastat command

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

9. Solaris

metastat |grep Needs

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

10. Solaris

Metastat shows state needs maintenance

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
Mail::Transport::Exim(3pm)				User Contributed Perl Documentation				Mail::Transport::Exim(3pm)

NAME
Mail::Transport::Exim - transmit messages using external Exim program INHERITANCE
Mail::Transport::Exim is a Mail::Transport::Send is a Mail::Transport is a Mail::Reporter SYNOPSIS
my $sender = Mail::Transport::Exim->new(...); $sender->send($message); DESCRIPTION
Implements mail transport using the external 'Exim' program. When instantiated, the mailer will look for the binary in specific system directories, and the first version found is taken. METHODS
Constructors Mail::Transport::Exim->new(OPTIONS) If you have Exim installed in a non-standard location, you will need to specify the path, using new(proxy). -Option --Defined in --Default executable Mail::Transport undef hostname Mail::Transport 'localhost' interval Mail::Transport 30 log Mail::Reporter 'WARNINGS' password Mail::Transport undef port Mail::Transport undef proxy Mail::Transport undef retry Mail::Transport <false> timeout Mail::Transport 120 trace Mail::Reporter 'WARNINGS' username Mail::Transport undef via Mail::Transport 'exim' executable => FILENAME hostname => HOSTNAME|ARRAY-OF-HOSTNAMES interval => SECONDS log => LEVEL password => STRING port => INTEGER proxy => PATH retry => NUMBER|undef timeout => SECONDS trace => LEVEL username => STRING via => CLASS|NAME Sending mail $obj->destinations(MESSAGE, [ADDRESS|ARRAY-OF-ADDRESSES]) See "Sending mail" in Mail::Transport::Send $obj->putContent(MESSAGE, FILEHANDLE, OPTIONS) See "Sending mail" in Mail::Transport::Send $obj->send(MESSAGE, OPTIONS) See "Sending mail" in Mail::Transport::Send $obj->trySend(MESSAGE, OPTIONS) Server connection $obj->findBinary(NAME [, DIRECTORIES]) See "Server connection" in Mail::Transport $obj->remoteHost() See "Server connection" in Mail::Transport $obj->retry() See "Server connection" in Mail::Transport Error handling $obj->AUTOLOAD() See "Error handling" in Mail::Reporter $obj->addReport(OBJECT) See "Error handling" in Mail::Reporter $obj->defaultTrace([LEVEL]|[LOGLEVEL, TRACELEVEL]|[LEVEL, CALLBACK]) Mail::Transport::Exim->defaultTrace([LEVEL]|[LOGLEVEL, TRACELEVEL]|[LEVEL, CALLBACK]) See "Error handling" in Mail::Reporter $obj->errors() See "Error handling" in Mail::Reporter $obj->log([LEVEL [,STRINGS]]) Mail::Transport::Exim->log([LEVEL [,STRINGS]]) See "Error handling" in Mail::Reporter $obj->logPriority(LEVEL) Mail::Transport::Exim->logPriority(LEVEL) See "Error handling" in Mail::Reporter $obj->logSettings() See "Error handling" in Mail::Reporter $obj->notImplemented() See "Error handling" in Mail::Reporter $obj->report([LEVEL]) See "Error handling" in Mail::Reporter $obj->reportAll([LEVEL]) See "Error handling" in Mail::Reporter $obj->trace([LEVEL]) See "Error handling" in Mail::Reporter $obj->warnings() See "Error handling" in Mail::Reporter Cleanup $obj->DESTROY() See "Cleanup" in Mail::Reporter $obj->inGlobalDestruction() See "Cleanup" in Mail::Reporter DIAGNOSTICS
Error: Errors when closing Exim mailer $program: $! The Exim mail transfer agent did start, but was not able to handle the message correctly. Warning: Message has no destination It was not possible to figure-out where the message is intended to go to. Error: Package $package does not implement $method. Fatal error: the specific package (or one of its superclasses) does not implement this method where it should. This message means that some other related classes do implement this method however the class at hand does not. Probably you should investigate this and probably inform the author of the package. Warning: Resent group does not specify a destination The message which is sent is the result of a bounce (for instance created with Mail::Message::bounce()), and therefore starts with a "Received" header field. With the "bounce", the new destination(s) of the message are given, which should be included as "Resent-To", "Resent-Cc", and "Resent-Bcc". The "To", "Cc", and "Bcc" header information is only used if no "Received" was found. That seems to be the best explanation of the RFC. As alternative, you may also specify the "to" option to some of the senders (for instance Mail::Transport::SMTP::send(to) to overrule any information found in the message itself about the destination. SEE ALSO
This module is part of Mail-Box distribution version 2.105, built on May 07, 2012. Website: http://perl.overmeer.net/mailbox/ LICENSE
Copyrights 2001-2012 by [Mark Overmeer]. For other contributors see ChangeLog. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. See http://www.perl.com/perl/misc/Artistic.html perl v5.14.2 2012-05-07 Mail::Transport::Exim(3pm)
All times are GMT -4. The time now is 12:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy