- Community Home
- >
- Servers and Operating Systems
- >
- BladeSystem
- >
- BladeSystem Storage Blades
- >
- Re: Smartarray controller P812 firmware 3.52
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- Report Inappropriate Content
10-27-2010 06:35 AM
10-27-2010 06:35 AM
Smartarray controller P812 firmware 3.52
Daniel was looking for some customer info:
*********************
Hi Experts,
I've a customer who has updated his firmware to 3.52 after reading the
advisory below.
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c0254
7655
The customer is worried and wants to know he can know if he was already hit
by the issues described:
CUSTOMER ACTION REQUIRED to Avoid Potential for Incomplete or Problematic
Data Transfer Scenarios During Periods of Heavy I/O Involving Discontiguous
Write Operations. The customer wants to know how this issues would manifest themselves and
what the remediation steps would be (apart from the firmware upgrade of course). Consistency
checks of the hard disks?
************************
Mark had some info for Daniel's customer:
****************************
Consistency Checks of the Hard Drives are always being run in the background for Smartarrays. Depending on the size of the drive and the IO placed upon it, it may take a while to loop through one consistency check, but they're always on.
Unfortunately I don't know how this Data transfer scenario pans out. "Incomplete" or "Problematic" can address such wide ranging scenarios.
So regarding incomplete, if it means it's incomplete for the whole stripe, then a consistency check isn't going to call it out, but if its incomplete for a disk in the stripe then it most likely will as the XOR data will be wrong. I'm not sure you'll get a good answer on this. These advisories seem to be worded vaguely so they appear more toned down, and it's hard to get the real story sometimes.
Also, the other thing you've got to think about is generally, if it's not picked up by a consistency check, e.g the stripe is OK, then the next port of call is to check the backup logs on a full backup. Of course the file may have a block as an incomplete transfer, so it's not a 100% fool proof, but it gives you a warm and fuzzy on the file system itself, and the master file table.
****************************
Other comments or questions?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-28-2010 03:33 AM
10-28-2010 03:33 AM
Re: Smartarray controller P812 firmware 3.52
Hello,
i think i am the customer which is talked about here, and i really need something more than a "warm fuzzy feeling"!
The system is a DataCore SAN which is build from 336 disks in MSA 60 & MSA 2600 connected to 6 P812 controllers. All our company data is on that system. We had a similar problem in an old P800 firmware version with raid 5 (we had inconsistencies in our databases which was most critical) so that is the reason why we switched to raid 1 for the more important data (and so we have wasted much money on the additional disks).
I really cannot understand how something like this is taken so lightly by HP that we do not have an answer until now!
Markus Kretzer
Buhl Data Service GmbH
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP