Architectural extensions for memory mirroring at page granularity on demand
US-2024152281-A1 · May 9, 2024 · US
US9684554B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9684554-B2 |
| Application number | US-201313739251-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 11, 2013 |
| Priority date | Mar 27, 2007 |
| Publication date | Jun 20, 2017 |
| Grant date | Jun 20, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A system and method for using failure casting to manage failures in computer system. In accordance with an embodiment, the system uses a failure casting hierarchy to cast failures of one type into failures of another type. In doing this, the system allows incidents, problems, or failures to be cast into a (typically smaller) set of failures, which the system knows how to handle. In accordance with a particular embodiment, failures can be cast into a category that is considered reboot-curable. If a failure is reboot-curable then rebooting the system will likely cure the problem. Examples include hardware failures, and reboot-specific methods that can be applied to disk failures and to failures within clusters of databases. The system can even be used to handle failures that were hitherto unforeseen—failures can be cast into known failures based on the failure symptoms, rather than any underlying cause.
Opening claim text (preview).
What is claimed is: 1. A method of managing failures in a computing system, wherein the method is implemented at least partly by a device, and wherein the method comprises: detecting a failure of a first failure type in the computing system; casting the first failure type to a second failure type, different that the first failure type, wherein the second failure type has an associated failure recovery; and attempting to resolve the first failure type by using the failure recovery associated with the second failure type. 2. The method of 1 , wherein the attempting to resolve the first failure type by using the failure recovery associated with the second failure type occurs at boot and/or start-up time. 3. The method of 1 , wherein the computing system includes an array of devices and the first and second failure types are associated with failures of the array of devices. 4. The method of 1 , wherein the method further comprises: using a failure casting hierarchy in a script that includes a set of non-reboot curable failures that are checked at boot time, and if a device exhibits a failure upon bootup within the set of non-reboot-curable failures, then the disk is not added to the array of devices. 5. A device that includes one or more processors configured to manage failures in a computing system at least by: detecting a failure of a first failure type in the computing system; casting the first failure type to a second failure type, different that the first failure type, wherein the second failure type has an associated failure recovery; and attempting to resolve the first failure type by using the failure recovery associated with the second failure type. 6. The device of claim 5 , wherein the attempting to resolve the first failure type by using the failure recovery associated with the second failure type occurs at boot and/or start-up time. 7. The device of claim 5 , wherein the computing system includes an array of devices and the first and second failure types are associated with failures of the array of devices. 8. The device of claim 5 , wherein the one or more processors are further configured to: use a failure casting hierarchy in a script that includes a set of non-reboot curable failures that are checked at boot time, and if a device exhibits a failure upon bootup within the set of non-reboot-curable failures, then the disk is not added to the array of devices. 9. A non-transitory computer readable storage medium storing at least executable code for managing failures in a computing system, wherein the executable code when executed at least: detects a failure of a first failure type in the computing system; casts the first failure type to a second failure type, different that the first failure type, wherein the second failure type has an associated failure recovery; and attempts to resolve the first failure type by using the failure recovery associated with the second failure type.
in a storage system, e.g. in a DASD or network based storage system (drivers for digital recording or reproducing units G06F3/06; circuits for error detection or correction within digital recording or reproducing units G11B20/18; for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS], H04L67/1097) · CPC title
where the redundant component is memory or memory area · CPC title
Boot up procedures · CPC title
Management of state, configuration or failover · CPC title
by power-on test, e.g. power-on self test [POST] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.