- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE 3PAR StoreServ Storage
- >
- Spare chunklet and its behavior under disk failure
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
Discussions
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
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
11-27-2018 01:45 AM - edited 11-29-2018 07:31 PM
11-27-2018 01:45 AM - edited 11-29-2018 07:31 PM
Hi,
First, we have a 3PAR configuration of 2 CPGs with AO:
1. RAID 6, with 14 data and 2 parity for 16 FC 10K SAS HDDs
2. RAID 6 with 4 data and 2 parity for 6 SSDs
- Default CPG: FC (moves to SSDs nightly with scheduled AO)
- Total raw capacity: 29TB
- Allocated space: >85%. (about 14% of allocated space is usused spare chunklets)
As seen from our 3PAR space consumption, about 14% of allocated space is consumed by the system as unused spare chunklets.
Our questions:
1. In case there are not enough disks, will the system still keep building up the spare chunklets?
2. Say, if one SSD has failed and there is not enough space in the SSD tier, will data be relocated to the FC tier automatically?
3. What is the maximum number of FC and SSD disks we can afford to fail at the same time?
Thanks,
Darien
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2018 03:51 AM
11-29-2018 03:51 AM
SolutionHello Darienn,
1. No. The number of spare chunklets are fixed as per your SparingAlgorithm settings. The current setting can be seen by running the command 'showsys -param'. The available values are as below
Default (roughly 2.5% with minimums), Minimal (roughly 2.5% without minimums), Maximal (one disk's worth in every cage), and Custom (not managed automatically by the system).
If you need to alter this, use the command "setsys SparingAlgorithm <value>" and then "admithw". Normally you do not need to change the default settings.
2. Yes. If no spare chunklets available in SSD drives, the same will be allocated from FC drives if required
3. Since this array has RAID 6, it can withstand two drives failures in the same RAID set. If the question is related to spare chunklets, the array will use any free chunklets (if no spare chunklets available when a drive fails).
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
