Sponsored Content
Full Discussion: transport errors in iostat
Top Forums UNIX for Dummies Questions & Answers transport errors in iostat Post 302592963 by dyavuzy1 on Wednesday 25th of January 2012 10:18:00 AM
Old 01-25-2012
yes, both disks are mirrored, metareplace was invoked and problematic disk was resycned from its sub mirror..

Metastat does not return any message pointing disk need any maintenance process..but there is still some hard and transport errors on it, these errors are not incremented though..
 

10 More Discussions You Might Find Interesting

1. Solaris

PLOGI failed state=Packet Transport error

Someone who can help me. the following error occur, what does it mean, and any possible solution you can give.thanks syslog: fp: NOTICE: fp(2): PLOGI to d5900 failed state=Packet Transport error , reason=No Connection (Database) $cat /var/adm/messages Nov 3 05:16:21 vfaus279 fp: ... (7 Replies)
Discussion started by: o_m_g
7 Replies

2. Shell Programming and Scripting

Transport to another server within a script.

I'm not sure how to phrase this... We currently have a server that we have to load a special kind of file onto, to do this we have a script that someone on my team wrote years ago called emm <file>. We recently added another server to our system, so every file that's added on one has to be added... (2 Replies)
Discussion started by: DeCoTwc
2 Replies

3. Solaris

iostat -nE with Hard Errors

iostat -nE returns the followings I want to know what is happening to my StorEDGE A1000? Can someone help me? It is a critical device. (1 Reply)
Discussion started by: nickychung
1 Replies

4. UNIX for Advanced & Expert Users

Transport Error

Dear Friends, I am using Solaris 10 on Sun Sparc T5120 with 4 HDD(Raid).I am getting transport error in one of my mirrored HDD c1t2d0. Below is a screen shot. I have replaced the HDD with new one but still the same. Any one can help???? c1t2d0 Soft Errors: 0 Hard Errors: 0... (1 Reply)
Discussion started by: solaris5.10
1 Replies

5. Solaris

SC3.2 issue - cluster transport configuration not right - resulting fail

I am trying to set up a two host cluster. trouble is with the cluster transport configuration. i'm using e1000g2 and g3 for the cluster transport. global0 and global1 are my two nodes, and I am running the scinstall from global1. i think i should be expecting, is this: The following... (19 Replies)
Discussion started by: frustin
19 Replies

6. Solaris

What is the difference between softerrors,harderrors,transport errors?

what is the difference between softerrors,harderrors,transport errors? (3 Replies)
Discussion started by: tv.praveenkumar
3 Replies

7. Solaris

iostat -En errors

I all, I would like to know what are the causes of : -soft error -harderror -transport error and how to avoid and repare them. I got the iostat out put below: atng-mm01% iostat -En | grep -i hard c0t0d0 Soft Errors: 1 Hard Errors: 0 Transport Errors: 0 c0t0d1 ... (3 Replies)
Discussion started by: zaza
3 Replies

8. Programming

Problem transport endpoint is not connected

i've made a simple program that change a string from lowercase to uppercase and from uppercase to lowercase. Server works until start client, after client run server give this error: "recv server fallita: Transport endpoint is not connected" why? i think that stream closed too soon or not? below... (1 Reply)
Discussion started by: tafazzi87
1 Replies

9. Solaris

getpeername: Transport endpoint is not connected

Hi Folks, I am getting the following error in /var/adm/messages. Can any one help me out on this? ZXXXXXA:/# tail /var/adm/messages Oct 26 00:13:04 ZXXXXXA ftpd: setsockopt SO_KEEPALIVE Invalid argument Oct 26 00:13:04 ZXXXXXA ftpd: setsockopt (SO_OOBINLINE): Invalid argument Oct 26... (3 Replies)
Discussion started by: vivek.goel.piet
3 Replies

10. Solaris

Sense key unit attention & iostat hardware and transport errors on SAN disks

Hello, I'm trying to get to the bottom of SAN disk errors we've been seeing. Server is Sun Fire X4270 M2 running Solaris 10 8/11 u10 X86 since April 2012. SAN HBAs are SG-PCIE2FC-QF8-Z-Sun-branded Qlogic. SAN storage system is Hitachi VSP. We have 32 LUNs in use and another 8 LUNs not brought... (4 Replies)
Discussion started by: TKD
4 Replies
volmirror(8)						      System Manager's Manual						      volmirror(8)

NAME
volmirror - Mirrors volumes on a disk or control default mirroring SYNOPSIS
/usr/sbin/volmirror [-g diskgroup] [-d yes|no] medianame [new_medianame...] /usr/sbin/volmirror [-g diskgroup] [-d yes|no] -a [new_medianame...] /usr/sbin/volmirror [-g diskgroup] [-d yes|no] /usr/sbin/volmirror [-g diskgroup] -D OPTIONS
The volmirror command supports the following options: Limits operation of the command to the given disk group, as specified by disk group ID or disk group name. The medianame operands will be evaluated relative to the given disk group. If no disk group is supplied to the volmirror command, rootdg is presumed. Changes the default for subsequent volume creation, depending on the option argument. If the option argument is yes, all subsequent volumes created using the volassist command will automatically be created as mirrored volumes. If the option argument supplied is no, mirroring will be turned off for future volumes by default. Displays current default status for mirroring. Mirrors all existing volumes for the specified disk group. DESCRIPTION
The volmirror command provides a mechanism to mirror all the contents of a specified disk, to mirror all currently unmirrored volumes in the specified disk group, or to change or display the current defaults for mirroring. All volumes that have only a single plex (mirror copy), will be mirrored by adding an additional plex. Volumes containing subdisks that reside on more than one disk will not be mirrored by volmirror. The volmirror command is generally called from the voldiskadm menus. It is not an interactive command and once called, will continue until completion of the operation or until a failure is detected. Note Due to the nature of generating mirror copies of volumes, this command may take a considerable time to complete. In the first listed form of the command, the disk media name is supplied on the command line to volmirror. That name is taken to be the only disk from which volumes should be mirrored. In the case of mirroring volumes from a specified disk, only simple single-subdisk volumes are mirrored. In the first and second listed forms of the command, the new_medianame ... parameter identifies a new disk media name (or set of names). The mirroring operation being performed will use these names as targets on which to allocate the mirrors. An error will result if the same disk is specified for both the source and target disk and if no other viable targets are supplied. EXAMPLES
The following are examples of the use of the volmirror command. The following command mirrors the contents of the disk named disk01 to any available space on any available disk. Subsequent calls to volassist will cause created volumes to be mirrored by default. volmirror -d yes disk01 The following command displays the current status of default mirroring. It prints the string yes if mirroring is currently enabled or no, if not. volmirror -D The following command mirrors any volumes on disk02 onto disk03. volmirror disk02 disk03 FILES
The defaults file for volassist parameters. SEE ALSO
volintro(8), volassist(8), volrootmir(8) volmirror(8)
All times are GMT -4. The time now is 02:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy