- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- EVA 8100 wrong number of allocated GBs displayed
Disk Enclosures
1748151
Members
3906
Online
108758
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
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
тАО03-16-2011 05:02 AM
тАО03-16-2011 05:02 AM
We mirror two EVA 8100 with 70 disks each in default DGs and observe that as disks get replaced the numbers of allocated GBs on the two sides of the mirror drift hundreds of gigabytes apart and never level back until controllers in one or other EVA are re-booted, usually the more highly allocated side but occasionally the other side too has to be re-booted to force the two EVAs to show the exact same allocated size as should be expected due to the absolutely equal allocation policy on both sides of the mirror.
The firmware is 6220, the most up-to-date.
Is there a less intrusive way to flush the correct values of allocated space to the CommandView tool ?
Re-booting a controller has consequences for the client systems because hardware paths leading to a re-booting controller may need minutes to fail-over to an alternate path via a still running controller.
For a product in its 6th incarnation (F/W 6220) one would expect diagnostic tools to display reliable values without having to resort to crude arm-twisting, but HP seems loath to address the issue, probably because most users don't mirror their EVAs and are not even aware that something's wrong until the discrepancy causes the value of "Allocated" to exceed the value of "Total", in which case HP suggests to re-boot the system as a aquick fix.
So long as HP doesn't fix the root problem we are stuck with re-boots, but how to minimize the impact on the running clients ?
We can locate the respective controller for each hardware path but how to temporarily promote a still running path as preferable even though it is not the best one due to the asymetric nature of controller-disk interconnects ? Auto-path algorithms in HP-UX 11.31 might even actively obstruct such attempts at prioritizing.
Shorten the IO_TIMEOUT ? Sounds too risky but who knows ?
The firmware is 6220, the most up-to-date.
Is there a less intrusive way to flush the correct values of allocated space to the CommandView tool ?
Re-booting a controller has consequences for the client systems because hardware paths leading to a re-booting controller may need minutes to fail-over to an alternate path via a still running controller.
For a product in its 6th incarnation (F/W 6220) one would expect diagnostic tools to display reliable values without having to resort to crude arm-twisting, but HP seems loath to address the issue, probably because most users don't mirror their EVAs and are not even aware that something's wrong until the discrepancy causes the value of "Allocated" to exceed the value of "Total", in which case HP suggests to re-boot the system as a aquick fix.
So long as HP doesn't fix the root problem we are stuck with re-boots, but how to minimize the impact on the running clients ?
We can locate the respective controller for each hardware path but how to temporarily promote a still running path as preferable even though it is not the best one due to the asymetric nature of controller-disk interconnects ? Auto-path algorithms in HP-UX 11.31 might even actively obstruct such attempts at prioritizing.
Shorten the IO_TIMEOUT ? Sounds too risky but who knows ?
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2011 12:54 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2011 01:57 AM
тАО03-17-2011 01:57 AM
Re: EVA 8100 wrong number of allocated GBs displayed
... where under fixes one finds:
Addressed an issue in the controller software that led to incorrect capacity reporting when
ungrouping and grouping drives.
Sounds like the problem I described. I'll reserve the Easter break to update firmware.
Kudos, Victor,
It's only been out since a couple of days!
Addressed an issue in the controller software that led to incorrect capacity reporting when
ungrouping and grouping drives.
Sounds like the problem I described. I'll reserve the Easter break to update firmware.
Kudos, Victor,
It's only been out since a couple of days!
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