- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: EVA 8000 and AIX 5.3 TL5
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
тАО04-25-2008 09:25 AM
тАО04-25-2008 09:25 AM
My question is: Does HP recommend that bad block reallocation be turned off on the OS level? If so can you point me into the location of some documentation surrounding that.
I've worked with EMC in the past and I know they recommend it but I'm not sure about this IBM gear.
Thanks
-jim
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2008 12:53 AM
тАО04-26-2008 12:53 AM
Re: EVA 8000 and AIX 5.3 TL5
From the http://www.redbooks.ibm.com/abstracts/SG245432.html?Open
it is clear that IBM recommendation is to disable the bad block reallocation on the concurrent access VGs/every logical volume.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-28-2008 01:09 PM
тАО04-28-2008 01:09 PM
Re: EVA 8000 and AIX 5.3 TL5
Thanks for the reply. I knew the EMC and HP server settings. And i as well, assume it'd be the same for EVA and AIX gear. I'm not running concurrent (mulitple servers seeing same drives at the same time) so I couldn't find in that document anything that was definitive. Thanks for the help though.
-jim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-29-2008 08:58 AM
тАО04-29-2008 08:58 AM
Re: EVA 8000 and AIX 5.3 TL5
I've never seen anything in the HP doc about this, and here we have never done this. We have many aix systems booting and using data disks served up by EVA arrays.
Could you provide more info about the errors you encountered, and the software you are using (MPIO, antemeta, etc...)? Would be very interested in what happened, and under what circumstances. Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-29-2008 09:20 AM
тАО04-29-2008 09:20 AM
Re: EVA 8000 and AIX 5.3 TL5
Here we boot off of the SAN drives. Three of our servers suffered OS corruption. We were luck to have an old multibos image to boot off of to fsck the system systems. The SAN guys were unable to determine if these all shared the same physical drive in the EVA. The core issue may have been something else but if brought up to my attention that maybe we should have the OS level bad block reallocation turned off. On some of our servers we do run MPIO. I wish this issue was as cut and dry with the issues but it's not. One server experienced issues running simple commands like ls or lsattr while others simply just hung. So anytime I witness unexplainable events like this, I found it to be related to bad block reallocation. So for all the words here but my posting at this point was mostly trying to determine best practices for the EVA and IBM. I know EMC provides this info but I'm not so sure I can find anything related to this combination. I agree that it works fine for the longest time but if you ever get a strange event that's unexplainable but a "reboot" fixes then you'd know what I'm talking about.
I will pay more attention to patterns but at this point they're all P570 Lpars running their OS on EVA 8000.
-peace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-30-2008 02:19 PM
тАО04-30-2008 02:19 PM
Re: EVA 8000 and AIX 5.3 TL5
It sounds like you are saying a physical disk failure on the EVA that seemed to precipitate the outage you had, is that correct? I say this because of your comment about systems sharing a physical disk.
It's easy to dertermine whether systems are using a certain disk -- all vdisks in a disk group share all the physical disks in that group.
Unless the vdisks are vraid0, a single disk failure should not affect the operation of vdisks.
Your post is the first I've heard about BB relocation policy for san devices...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-05-2008 01:59 PM
тАО05-05-2008 01:59 PM
Re: EVA 8000 and AIX 5.3 TL5
As for the issues I had, they've all been resolved by running fsck and usually that would end this until the next time but this time I'm not going to let it go until I find what I'm looking for.
Thanks for reading.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-05-2008 04:02 PM
тАО05-05-2008 04:02 PM
SolutionHi Jim, If you had a bad block on an EVA phsyical disk it should be dealt with on the array and never get back to the hosts systems that are using it. That's one of the big benefits of virtualizing storage.
But I say "should" because it seems that over the years we've been using EVA storage, messages DO sometimes get sent back to the host about back-end events, in the form of 'inquiry data has changed' UNIT ATTENTIONS. These can confuse some systems that aren't expecting them, and can cause error counters to increment, and device drivers to go through needless error recovery.