- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: optimum hba queue depth
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-30-2009 06:09 PM
тАО09-30-2009 06:09 PM
optimum hba queue depth
Hi.
i have an sles9 using qlogic HBA w/ a default queue depth of 16. this is connected to an msa2000. i increased the hba queue depth to 64 hoping to increase i/o performance but got scsi busy errors (0x20000). Do you guys know how to check the msa2000 queue depth so i can base my hba adjustments from that?
thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-01-2009 01:54 AM
тАО10-01-2009 01:54 AM
Re: optimum hba queue depth
---
options qla2xxx ql2xmaxqdepth=16 qlport_down_retry=10 ql2xloginretrycount=30
---
in /etc/modprobe.conf?
Also, are you using multipath? If this is the case, edit /etc/multipath.conf following this schema (VALID FOR MSA2012fc/MSA2212fc/MSA2012i. If you have another model, the values may differ!)
---
# COMMENT THE WHOLE BLACKLISTED DEVICES SECTION ON TOP
# TO ENABLE HP+QLOGIC MULTIPATH
### ADD THE FOLLOWING BLACKLIST AFTER"defaults user_friendly_names yes" SECTION
## Blacklist non-SAN devices
devnode_blacklist {
devnode "^sd[a-z]"
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
devnode "^hd[a-z]"
devnode "^cciss!c[0-9]d[0-9]*"
}
# add the following under "devices" (UNCOMMENT THE SECTION FIRST!!!)
# section:
# For MSA2012fc/MSA2212fc/MSA2012i
device
{
vendor "HP"
product "MSA2[02]12fc|MSA2012i"
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
hardware_handler "0"
path_selector "round-robin 0"
path_grouping_policy multibus
failback immediate
rr_weight uniform
no_path_retry 18
rr_min_io 100
path_checker tur
}
---
Finally, have you rebuilt the initrd image used by the system at boot time? That could definitely be part of the issue, as in many cases (depending on vendor/OS coupling) if you don't do it, you don't have the correct values for all those parameters correctly set.
You can rebuild initrd image using "mkinitrd". Make sure you make a backup copy of your current initrd, and to modify your grub.conf file so that you can choose what initrd to use at boot time. Doing this, in the unfortunate event of something going wrong at the next boot with the new initrd, you can still boot using the old one. Kernel panic may happen, so do this on your responsibility.
HTH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-01-2009 02:37 AM
тАО10-01-2009 02:37 AM
Re: optimum hba queue depth
thanks for your reply. yup, basically, i've done all of those. for now i've reverted the change to do away w/ the errors. back to normal. i'm gonna try to check out what's the most optimal value for the queue depth. btw, have you tried checking out if your setup is able to maximize it's current queue depth?
cheers!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-01-2009 04:09 AM
тАО10-01-2009 04:09 AM
Re: optimum hba queue depth
Have you tried working on the opposite side, I mean, change some parms on the storage? A possible reason for the 0x20000 could be that no_path_retry is not enough to queue all the suff that's trying to get written to the disks. So you could try something like this in multipath.cfg:
no_path_retry "queue"
(and rebuild initrd). Doing so, you should be able to get the storage array to queue all the I/O, before failing a path or throwing errors there will be more "buffering" room. Keep in mind that if you have REAL reason for that 0x20000 error, with this setting you could maybe avoid the error but everything could anyway result in a very slowly responding system, because of the "queue".
On the HBA side, you could work a bit on the disk timeout settings (check qlogic website for info)...
Hopefully somebody else in the forum will ass more ideas.
Bye!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-01-2009 04:10 AM
тАО10-01-2009 04:10 AM