Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory What should I do with this metastat result? metareplace everything? Post 302269125 by nickychung on Wednesday 17th of December 2008 12:38:12 AM
Old 12-17-2008
Yes, I am still able to access d0 but not d6. d0 is online. d6 is dead.

But metareplace just can't help me to fix the "needs maintenance" problem.

iostat -nE returns:

Quote:
c0t0d0 Soft Errors: 0 Hard Errors: 3 Transport Errors: 9
Vendor: SEAGATE Product: ST318203LSUN18G Revision: 034A Serial No: LRD9164600001037
Size: 18.11GB <18110967808 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 3 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
c0t1d0 Soft Errors: 0 Hard Errors: 4 Transport Errors: 2
Vendor: FUJITSU Product: MAG3182L SUN18G Revision: 1111 Serial No: 02542399
Size: 18.11GB <18110967808 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 4 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
c0t6d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: TOSHIBA Product: XM6201TASUN32XCD Revision: 1103 Serial No: 12/12/97
Size: 18446744073.71GB <-1 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
 

10 More Discussions You Might Find Interesting

1. Solaris

SVM metastat -- needs maintenance

Running Solaris 9 with SVM. I'm not that familiar with it, but metastat output gives "needs maintenance" message on 2 of the mirrors. There are no errors in /var/adm/messages. What do I need to do to fix this error? Thanks. (14 Replies)
Discussion started by: dangral
14 Replies

2. 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

3. Solaris

metareplace error

Hello guys, i am getting some errors as below when i want to perform maintainence on the disks of my servers, getting errors like this "metareplace: myhost: /dev/dsk/c1t0d0s5: Invalid argument" when i execute #metareplace -e d5 c1t0d0s5 kindly advise on this matter,am afraid to use -f... (4 Replies)
Discussion started by: cromohawk
4 Replies

4. 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

5. Solaris

Urgent- metareplace -e write errors

I have a disk in maintanance status . I executed metareplace -e partition device . It resynced upto 5 % and then stopped . In the /var/adm/messages it showed the write error . My question is if I analyse and repair the disk in format command , will my write error go . I dont have 0 hard and... (6 Replies)
Discussion started by: Hitesh Shah
6 Replies

6. 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

7. 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

8. Solaris

DiskSuite State Unavailable After metareplace

Hello, After replacing a JBOD disk that died, the metareplace was ran, the device went into enable/sync'ing state and then when the sync completed, the state changed to unavailable. metadb shows the replica db looking good on the new disk. format shows the disk online and looking good. ... (2 Replies)
Discussion started by: rfransix
2 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 09:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy