- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- XP256; pvtimeouts and queue depth
Disk Enclosures
1748283
Members
3977
Online
108761
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
02-08-2001 10:39 AM
02-08-2001 10:39 AM
XP256; pvtimeouts and queue depth
I'm hoping to get some honest feed back here, from customers using the XP256, preferably connected in a SAN environment, with switches.
We've got the XP, with just an R1 cabinet, almost full, all 47 gig disks, configured as Open-9s. We're FC attached from the A, E, and J ports to a pair of brocade switches. Off the switches we've got fc attached a K460, K570, and 3 N4000 servers. The two K's are running flat file JFS file systems, while the N's are our SAP environment. On only the K460 we're fighting regular LVM PowerFail events, 99% of the time it's 2 ldevs involved, and they always report back in within the same second of the PF events. We've attempted to replicate the problem on the K570, no such luck, it behaves exactly as we expect it to-great!
All pvtimeouts are set to the default, as is the queue depth. We've found that extending the pvtimeout only serves to quiet the PowerFail messages, the affected process runs 5-10 times as long as it does with the powerfails.
Is anyone else seeing oddities similar to this, and if so, what are your pvtimeouts set to, and queue depth?
Many thanks to all who respond!
We've got the XP, with just an R1 cabinet, almost full, all 47 gig disks, configured as Open-9s. We're FC attached from the A, E, and J ports to a pair of brocade switches. Off the switches we've got fc attached a K460, K570, and 3 N4000 servers. The two K's are running flat file JFS file systems, while the N's are our SAP environment. On only the K460 we're fighting regular LVM PowerFail events, 99% of the time it's 2 ldevs involved, and they always report back in within the same second of the PF events. We've attempted to replicate the problem on the K570, no such luck, it behaves exactly as we expect it to-great!
All pvtimeouts are set to the default, as is the queue depth. We've found that extending the pvtimeout only serves to quiet the PowerFail messages, the affected process runs 5-10 times as long as it does with the powerfails.
Is anyone else seeing oddities similar to this, and if so, what are your pvtimeouts set to, and queue depth?
Many thanks to all who respond!
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2001 12:07 AM
02-09-2001 12:07 AM
Re: XP256; pvtimeouts and queue depth
We had also this problem with similar config (hub and not switch for SAN). I modify pvtimeout to 60 and qdepth to 2. Since that we have no more message. This value MUST be reset at each boot. So we add and /sbin/init.d/initdsk with /etc/rc.config.3/Sxxxinitdsk link.
Thind these script as attachment . Qdepth is configurable so that total qdepth is less than 256 on one FC link.
Here is the config file of attached script:
# config init de physical volumes pour XP256
# racine de l'adresse des disques
export ADDISK=c6t
# time out PV
export PVTO=60
# Q DEPTH "normale"
export QDEPTH=2
# Q DEPTH "speciale"
export SQDEPTH=2
# liste des device avec une QDEPTH speciale
# attention le nb total de qdepth doit etre < 256 par device
# pour temp tape4 tape2
#export LDEV="c13t3d3 c13t0d2"
export LDEV=""
Thind these script as attachment . Qdepth is configurable so that total qdepth is less than 256 on one FC link.
Here is the config file of attached script:
# config init de physical volumes pour XP256
# racine de l'adresse des disques
export ADDISK=c6t
# time out PV
export PVTO=60
# Q DEPTH "normale"
export QDEPTH=2
# Q DEPTH "speciale"
export SQDEPTH=2
# liste des device avec une QDEPTH speciale
# attention le nb total de qdepth doit etre < 256 par device
# pour temp tape4 tape2
#export LDEV="c13t3d3 c13t0d2"
export LDEV=""
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP