- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- IO Timeout for Fibre Channel Attached Disks
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
тАО10-28-2002 05:13 AM
тАО10-28-2002 05:13 AM
I notice the timeout for switching between fibre channel disks (alternate links) is about a minute. I know this can be changed with pvchange but it says the default is to use the driver's timeout. I have two A6685A cards.
Are there any cons to setting the timeout lower then the default? A minute seems like a lot of time to fail to the next disk/path.
Also, as the disks are on a SAN (IBM Shark) and not locally attached should I disable bad block relocation? I assume so but wanted to double check. If I should disable this, how do I do it?
Thanks!
- Justin
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2002 05:21 AM
тАО10-28-2002 05:21 AM
SolutionAll your questions are HARDWAREdependent, so check with your vendor (IBM in this case). In my environment (EMC ClarIIon and Symmetrix) we use the following :
# Timeout parameter
pvchange -t 180 /dev/dsk/
# Bad block relocation
lvcreate -L
But like I said, it depends !
Regards,
Tom
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2002 05:28 AM
тАО10-28-2002 05:28 AM
Re: IO Timeout for Fibre Channel Attached Disks
don't know about the shark but typically with EMC or RAID boxes in general you should disable Bad Block relocation since the Array has its own way of dealing with such things.
Also timeout ist usually set to a higher value than default....
options to use:
pvchange -t 180 /dev.....
lvcreate -r N .....
Regards
Bernhard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2002 07:44 AM
тАО10-28-2002 07:44 AM
Re: IO Timeout for Fibre Channel Attached Disks
Generally I have seen a timeout of 180 sec is very good , with disks on fibre channel . I haven't dealt with IBM SHARK , but on EMC , hitachi , XP256 and Compaq SAN , the value of 180 sec , is good enough .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2002 10:05 AM
тАО10-28-2002 10:05 AM
Re: IO Timeout for Fibre Channel Attached Disks
Anyone know why the timeout is so long? Failing between alternate links would cause the application to possibly freeze for a minute or two while this happens. I assume there is a reason for the timeout to be as high as it is (as the default is or as suggested here).
Thanks,
- Justin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2002 01:07 PM
тАО10-28-2002 01:07 PM
Re: IO Timeout for Fibre Channel Attached Disks
The timeout is set high, so the disk array can complete it's task internally without having to report errors like "SCSI lbolt" back into your system log.