07-15-2003
From Sunsolve:
Quote:
Solaris[TM] sd driver taq queuing problems/sd_max_throttle
How does one fix SCSI disk tag queuing problem?
By setting sd_max_throttle, in /etc/system, to a lower value.
sd_max_throttle, a sd driver tunable parameter, determines the max
number of commands that can be queued up by sd to be submitted to the
HBA (Host Bus Adapter) driver. By default, sd_max_throttle is 256.
Since SCSI tag queuing, SCSI_OPTIONS_TAG (0x80), is enabled by default
in Solaris, when the disk controller is fully populated with targets
or having very fast disks (e.g., RAID devices), commands can be queued
up too fast (and reach the limit of 256) for sd driver to handle.
Once this condition is met, tagged command time-outs/retries or SCSI
transport failure messages often are displayed:
-> WARNING: /io-unit@f,e1200000/sbi@0,0/dma@0,81000/esp@0,80000 (esp1):
-> Disconnected tagged cmds (1) timeout for Target 1.0
-> WARNING: /io-unit@f,e1200000/sbi@0,0/dma@0,81000/esp@0,80000/sd@1,0 (sd16):
-> Error for command 'write' Error Level: Retryable
-> WARNING: /io-unit@f,e0200000/sbi@0,0/dma@0,81000/esp@0,80000/sd@3,0 (sd3):
-> SCSI transport failed: reason 'timeout': retrying command
-> WARNING: /io-unit@f,e0200000/sbi@0,0/dma@0,81000/esp@0,80000/sd@3,0 (sd3):
-> unix: SCSI transport failed: reason 'incomplete': retrying command
Setting sd_max_throttle to use a much smaller value, such as < 256, can fix
the problem.
To what value should sd_max_throttle be set? That depends on how many SCSI
targets are in the system. To have total queued commands < 100 can be a
workable rule (e.g., if there are 6 fast SCSI targets), and if sd_max_throttle
is set to be 16, the total queued commands can be 96. If tagged command
timeouts still are seen, then in /etc/system:
set sd:sd_max_throttle = 16
Suggest you go to
Sunsolve and do a search as there is other information. If you have a contract with Sun (or if you are on warrenty), give them a call.
If not, post what OS/version, and the rest of the error message.
9 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
guys,
pls help me out.
i hv good idea in redhat linux
in what areas i need 2 concentrate 2 mk me much
familiar with that of solaris.
:confused: pls let me know the major diff found in these two
os. (1 Reply)
Discussion started by: sriram.s
1 Replies
2. AIX
hi what is meant by major no in vg
what is meant by concurrent vg
i cant understand these two things (3 Replies)
Discussion started by: senmak
3 Replies
3. Shell Programming and Scripting
Hi,
I have line like this :
proj_name/module/trunk/module_1_0
where the first "1" refers to major version and second "0" refers to minor version.
any AWK or command like that so that I can filter out the major and minor ?
like major= command | input line
minor= command |... (4 Replies)
Discussion started by: bhaskar_m
4 Replies
4. UNIX and Linux Applications
Hi there all
I am going to be a new admin (AIX,Redhat,Suse, and Solaris).
I know these OS's at basic to intermediate level..somewhat.
i would like to know what are corporate level sys admin softwares that are commanly used day to day .
i know its a broad question. but i just wanna know few... (2 Replies)
Discussion started by: dplinux
2 Replies
5. AIX
HI All,
I would like to know is it compulsory to keep major number of shared VG's on cluster nodes to be same..?
I have come across a situation where on one node major number of shared vg is the major number of altinst_rootvg on other node..how to overcome this situation..?
shan (3 Replies)
Discussion started by: to_bsr
3 Replies
6. Shell Programming and Scripting
Hello, I have many lengthy files that need to be reformatted. I was hoping a sed or awk script could fix this.
Here is an example of the original format:
P0037
# Degree: 32.999981
# COMMAND: 03 (#01A) Scale 1.296875, 52 (Wooden Crate w/ #2 Label, Bahko)
v -3328.000000 12.101541 437.000000... (2 Replies)
Discussion started by: Blue Solo
2 Replies
7. UNIX for Dummies Questions & Answers
I am a new software developer and I wish to sell my software. I recently realized that from C++ code we can not stop the user seeing parts of the code that are related to scripts or system commands.
Would you make some comments on how software written in C++/JAVA (distributed via CD-ROMs or... (2 Replies)
Discussion started by: frad
2 Replies
8. What is on Your Mind?
Dear fellow *nixers,
please join me congratulating Corona688 for reaching the lonesome, lorn landmark of 4500 thanks! What an achievement in the gruelling ordeal of servicing these fora.
Incredible. All the best
RĂ¼diger (9 Replies)
Discussion started by: RudiC
9 Replies
9. What is on Your Mind?
Regarding the latest version of the UserCP prototype (version 0.63) I have made a lot of major changes, including
Added a "Posts Timeline" table for the recent posts, complimenting the non-table version earlier, which has been moved off the main menu (link at the bottom of the table).
Added a... (4 Replies)
Discussion started by: Neo
4 Replies
LEARN ABOUT HPUX
scsi_max_qdepth
scsi_max_qdepth(5) File Formats Manual scsi_max_qdepth(5)
NAME
scsi_max_qdepth - maximum number of I/Os that target will queue up for execution (OBSOLETE)
VALUES
Failsafe
Default
Allowed values
Recommended values
Most SCSI-2 and above devices accept multiple commands and have enough internal memory to support the default queue depth set by HP. You
may change the default value to tune devices for higher throughput or load balancing.
DESCRIPTION
Note: This tunable is obsolete and is replaced by the attribute which can be set through the command. See scsimgr(1M).
Some SCSI devices support tagged queuing, which means that they can have more than one SCSI command outstanding at any point in time. The
number of commands that can be outstanding varies by device, and is not known to HP-UX. To avoid overflowing this queue, HP-UX will not
send more than a certain number of outstanding commands to any SCSI device. This tunable sets the default value for that limit. The
default value can be overridden for specific devices using
Queue depth is synonymous to the tagged queuing. When supported by a target, it allows the target to accept multiple SCSI commands for
execution. Some targets can allow up to 256 commands to be stored from different initiators. This mechanism can help optimization for
better performance. Once the target command queue is full, the target terminates any additional I/O and returns a status to the initiator.
Targets may support less than 256 commands to be queued, hence the factory defaults to
If the system has a combination of devices that support small and larger queue depths, then a queue depth can be set to a value which would
work for most devices. For specific devices, the system administrator can change the queue depth on a per device basis using See
scsictl(1M) for more on how to use
The values for both 32-bit and 64-bit kernel are the same.
Who Is Expected to Change This Tunable?
Anyone.
Restrictions on Changing
Changes to this tunable take effect immediately.
When Should the Value of This Tunable Be Raised?
SCSI devices that have enough memory to support higher queue depth than the default set by HP. Such devices may offer better performance
if the queue depth is set to a higher value.
What Are the Side Effects of Raising the Value of This Tunable?
The queue depth applies to all the SCSI devices that support tag queuing. Setting the queue depth to a value larger than the disk can han-
dle will result in I/Os being held off once a condition exists on the disk. A mechanism exists that will lower the queue depth of the
device in case of condition avoiding infinite conditions on that device. Nevertheless, this mechanism will periodically try higher queue
depths and conditions will arise.
When Should the Value of This Tunable Be Lowered?
When the connected SCSI devices support smaller queue depth or for load balancing.
What Are the Side Effects of Lowering the Value of This Tunable?
Devices that support higher queue depth may not deliver optimal performance when a lower queue depth value is set.
What Other Tunables Should Be Changed at the Same Time?
None.
WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter has been obsoleted for HP-UX 11i Version 3.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by HP.
SEE ALSO
scsictl(1M), ioctl(2), scsi(7).
OBSOLETE
Tunable Kernel Parameters scsi_max_qdepth(5)