Sponsored Content
Full Discussion: transport errors in iostat
Top Forums UNIX for Dummies Questions & Answers transport errors in iostat Post 302592958 by vbe on Wednesday 25th of January 2012 10:10:11 AM
Old 01-25-2012
Are the disks in mirror?
These are non OS disks are they? (If mirror...)
 

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
iostat(1)						      General Commands Manual							 iostat(1)

NAME
iostat - Reports I/O statistics SYNOPSIS
iostat [drive...] [interval] [count] OPERANDS
Forces iostat to display specific drives. If drive is not specified (or the specified drive does not exist on the system or cluster, iostat displays the first two drives (even if more than two disk drives are configured in the system). Causes iostat to report once each interval seconds. The first report is for all time since the system was last booted, and each subsequent report is for the last interval only.The value must not be 0. Specifies the number of reports. For example, iostat 1 10 would produce 10 reports at 1-second intervals. You cannot specify count without interval because the first numeric argument to iostat is assumed to be interval. DESCRIPTION
The iostat command reports the following information: For terminals (collectively), the number of characters read and written per second. For each disk, the number of transfers per second and bytes transferred per second (in kilobytes). For the system, the percentage of time the system has spent in user mode, in user mode running low priority (nice) processes, in system mode, and idling. To compute this information, iostat counts data transfer completions, the number of words transferred for each disk, and the collective number of input and output characters for terminals. Also, each sixtieth of a second, iostat examines the state of each disk and makes a tally if the disk is active. When you issue an iostat command on a cluster member, it displays statistics only for those disks that are local to the member and that member's usage of those shared disks that it has mounted. It displays 0 for other disks in the cluster (those it doesn't have mounted), regardless of whether they are on the shared bus or are local to some other member. EXAMPLES
The output from this example displays cpu, terminal, and disk statistics for the first two disks on the system providing 5 reports at 1 second intervals: # iostat 1 5 tty floppy1 dsk9 cpu tin tout bps tps bps tps us ni sy id 0 3 0 0 0 0 1 0 4 95 4 58 0 0 0 0 1 0 2 97 1 53 0 0 0 0 0 0 2 98 5 59 0 0 0 0 1 0 1 98 6 60 0 0 0 0 1 0 2 97 The second example specifies device names in the command: # iostat dsk2 dsk3 cdrom2 tty dsk2 cdrom2 dsk3 cpu tin tout bps tps bps tps bps tps us ni sy id 0 13 11 5 5 2 2427 1213 0 1 1 98 SEE ALSO
Commands:vmstat(1) iostat(1)
All times are GMT -4. The time now is 10:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy