SOLID-STATE DISK (SSD) MANAGEMENT

• US 20130179631A1
• Filed: 11/02/2010
• Published: 07/11/2013
• Est. Priority Date: 11/02/2010
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Inventors: Cepulis, Darren J.
• Granted Patent: US 9,195,588 B2
• Time in Patent Office: Days
• US Class Current: 711/103
• CPC Class Codes: G06F 12/0246 in block erasable memory, e.g. flash memory
• CPC Class Codes: G06F 2206/1012 Load balancing
• CPC Class Codes: G06F 2212/7211 Wear leveling
• CPC Class Codes: G06F 3/0604 Improving or facilitating administration, e.g. storage management
• CPC Class Codes: G06F 3/0616 in relation to life time, e.g. increasing Mean Time Between Failures [MTBF]
• CPC Class Codes: G06F 3/0635 by changing the path, e.g. traffic rerouting, path reconfiguration
• CPC Class Codes: G06F 3/0644 Management of space entities, e.g. partitions, extents, pools
• CPC Class Codes: G06F 3/0653 Monitoring storage devices or systems
• CPC Class Codes: G06F 3/0679 Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]
• CPC Class Codes: G06F 3/0688 Non-volatile semiconductor memory arrays
• CPC Class Codes: G06Q 30/0631 Item recommendations
• CPC Class Codes: G11C 16/3495 Circuits or methods to detect or delay wearout of nonvolatile EPROM or EEPROM memory devices, e.g. by counting numbers of erase or reprogram cycles, by using multiple memory areas serially or cyclically

Abstract

SSD wear-level data (320) is generated on managed nodes (202) having SSDs (206). The wear-level data is collected by a management node (204).

Claims

1. A process (100;

404) comprising;

generating (101, 411) SSD wear-level data (320) on respective managed nodes (202); and

collecting (102;

412) said SSD wear-level data on a management node (204).

2. A process as recited in claim 1 wherein said collecting further includes storing in a database (212) of SSD wear data including said SSD wear-level data in association with data identifying the associated SSD and node.

3. A process as recited in claim 2 further comprising computing (413) wear-rate data and storing it in said database as part of said SSD wear data.

4. A process as recited in claim 1 further comprising planning (414) a workload redistribution (332) at least in part as a function of said SSD wear data.

5. A process as recited in claim 1 further comprising making purchase recommendations (328) at least in part as a function of said SSD wear data.

6. A computer system (200) comprising a management node (204) having an SSD data manager (324) configured to collect SAID wear-level data from managed nodes (202) haying SSDs (206), said management node including a processor (402), communications devices (404), and storage media (406).

7. A computer system as recited in claim 6 further comprising said managed nodes, at least one (304) of said managed nodes being configured to balance loads among other ones (302) of said managed nodes at least in part as a function of said wear-level data.

8. A computer system as recited in claim 6 wherein said management node includes an SSD purchase agent (326) configured to make recommendations (328) for purchasing replacement SSDs based at least in part on said SSD wear-level data.

9. A computer system as recited in claim 8 wherein said purchase agent is configured to make recommendations whether or not to replace a SSD with a hard disk based at least in part on said SSD wear-level data.

10. A computer system as recited in claim 6 wherein said management node includes a workload manager (330) configured to plan workload redistributions (332) on said managed node at least in part as a function of said SSD wear-level data.

11. A system (200) comprising storage media (406) encoded with code (408) configured to collect SSD wear level data (320) from managed nodes (202) haying SSDs (206).

12. A system as recited in claim 11 further comprising a processor (402) for executing said code.

13. A system as recited in claim 11 wherein said code is further configured to plan (414) workload redistributions (332) among said managed nodes at least in part as a function of said wear-level data.

14. A system as recited in claim 13 wherein said code is configured to plan said workload redistributions (232) so as to stagger the times at which the useful lives of said SSDs are projected to end.

15. A system as recited in claim 14 wherein said code is further configured to make recommendations (328) regarding the purchase of replacement SSDs for said managed nodes at least in part as a function of said wear-level data.