Sponsored Content
Full Discussion: transport errors in iostat
Top Forums UNIX for Dummies Questions & Answers transport errors in iostat Post 302592836 by vbe on Wednesday 25th of January 2012 04:47:32 AM
Old 01-25-2012
I suppose c1t1d0 and c1t0d0 are on the same controller? is it so?
Well you can be sure one of your disks is faulty and need attention...
 

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
re(7)							 Miscellaneous Information Manual						     re(7)

NAME
re - SWXCR RAID interface SYNOPSIS
2100 Server Model A500MP DEC SWXCR controller xcrn at * vector xcintr device disk renn at xcrn drive nn DESCRIPTION
The re driver is for the SWXCR RAID Array controller. The following rules are used to determine the major and minor numbers that are associated with an re type disk. There are two major num- bers used to represent re disks. The major numbers are 11 for block devices and 44 for character (raw) devices. The minor number is used to represent both the unit number and partition. A disk partition refers to a designated portion of the physical disk. To accomplish this reference, the 20-bit minor number is divided into three parts. The lowest six bits of the minor number specify a disk partition. The partitions use a letter, a through h, for their name. The next three bits of the minor number specify the RE unit number for a unit attached to an SWXCR controller. The final 11 bits specify the controller number. The device special file names associated with re disks are based on conventions that are closely associated with the minor number assigned to the disk. The standard device names begin with re for block special files and rre for character (raw) special files. Following the re is the unit number and then a letter, a through h, that represents the partition. Throughout this reference page, the question mark (?) character represents the unit number in the name of the device special file. For example, re?b could represent re0b, re1b, and so on. The unit number can be calculated if the major and minor numbers of an re disk are provided. For example, suppose you have a device spe- cial file rre6a, with a major number of 44 and a minor number of 384. The partition is represented by the lower six bits of the number 384. These lower six bits of the number 384 are 0, which specifies the a partition. The next three bits of the minor number 384 specify the unit number, which is 6. The next eleven bits specify the controller number, which is zero. Putting these three pieces together reveals that the major/minor number pair 44/384 refers to the a partition of unit 6 attached to controller number 0. A disk can be accessed through either the block special file or the character special file. The block special file accesses the disk using the file system's normal buffering mechanism. Reads and writes to the block special file can specify any size. This capability avoids the need to limit data transfers to the size of physical disk records and to calculate offsets within disk records. The file system can break up large read and write requests into smaller fixed size transfers to the disk. The character special file provides a raw interface that allows for direct transmission between the disk and the user's read or write buf- fer. A single read or write to the raw interface results in exactly one I/O operation. Consequently, raw I/O may be considerably more efficient for large transfers. For systems with RE disks, the first software boot after the system is powered on may take longer than expected. This delay is normal and is caused by the software spinning up the RE disks. Disk Support The RE driver handles all disk drives that can be connected to the SWXCR controller. To determine which drives are supported for specific CPU types and hardware configurations, see the Installation and Configuration Guide for the StorageWorks RAID Array 200 Subsystem Family. SWXCR RAID Controllers are viewed in all cases as RE type disks. There are some notable differences that should be taken into considera- tion when configuring a RAID device: Currently only sector sizes of 512 bytes are supported. Logical Volume sizes are not fixed sizes as compared to other disk devices. The size of the Logical Volume is configurable based on needs. The dynamic nature of Logical Volume sizes is dealt with by defining RAID devices as DYNAMIC. Only partitions a, b, c, and g are defined. If necessary, the disklabel(8) command can be run to change and define partitions for RAID devices. Usually, the re?a partition is used for the root file system and the re?b partition as a paging area. The re?c partition can be used for disk-to-disk copying because it maps the entire disk. The starting location and length (in 512 byte sectors) of the disk partitions of each drive are shown in the following table. Partition sizes can be changed by using the disklabel(8) command. SWXCR (RAID) partitions for systems based on the Alpha AXP architecture disk start length re?a 0 131072 re?b 131072 262144 re?c 0 end of media re?d 0 0 re?e 0 0 re?f 0 0 re?g 393216 end of media re?h 0 0 FILES
/dev/re??? /dev/rre??? /etc/disktab RELATED INFORMATION
disklabel(8), MAKEDEV(8), uerf(8) delim off re(7)
All times are GMT -4. The time now is 02:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy