Source: http://www.google.com/patents/US20060015771?dq=5,072,412
Timestamp: 2016-07-28 05:30:24
Document Index: 255705003

Matched Legal Cases: ['art 40', 'art 50', 'art 40', 'art 40', 'art 40', 'art 50', 'art 50', 'art 50', 'art 50', 'art 50', 'art 50', 'art 50', 'art 50', 'art 50']

Patent US20060015771 - Management method for spare disk drives a RAID system - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsA RAID system employs a storage controller, a primary storage array having a plurality of primary storage units, and a spare storage pool having one or more spare storage units. A method of operating the storage controller in managing the primary storage array and the spare storage pool involves a testing...http://www.google.com/patents/US20060015771?utm_source=gb-gplus-sharePatent US20060015771 - Management method for spare disk drives a RAID systemAdvanced Patent SearchPublication numberUS20060015771 A1Publication typeApplicationApplication numberUS 10/891,743Publication dateJan 19, 2006Filing dateJul 15, 2004Priority dateJul 15, 2004Also published asUS7533292Publication number10891743, 891743, US 2006/0015771 A1, US 2006/015771 A1, US 20060015771 A1, US 20060015771A1, US 2006015771 A1, US 2006015771A1, US-A1-20060015771, US-A1-2006015771, US2006/0015771A1, US2006/015771A1, US20060015771 A1, US20060015771A1, US2006015771 A1, US2006015771A1InventorsSteven Van Gundy, Michael Benhase, Brian Kraemer, Richard RipbergerOriginal AssigneeInternational Business Machines CorporationExport CitationBiBTeX, EndNote, RefManPatent Citations (13), Referenced by (37), Classifications (7), Legal Events (4) External Links: USPTO, USPTO Assignment, EspacenetManagement method for spare disk drives a RAID system
US 20060015771 A1Abstract
A RAID system employs a storage controller, a primary storage array having a plurality of primary storage units, and a spare storage pool having one or more spare storage units. A method of operating the storage controller in managing the primary storage array and the spare storage pool involves a testing by the storage controller of at least one repair service threshold representative of one or more operational conditions indicative of a necessity to repair at least one of the primary storage array and the spare storage unit, and a selective initiation by the storage controller of a repair service action for repairing one of the primary storage array and the spare storage unit based on the testing of the at least one repair service threshold. Images(8) Claims(20)
FIELD OF INVENTION [0001] The present invention generally relates to Redundant Array of Inexpensive Disks (“RAID”) technology. The present invention specifically relates to providing reliable backup for data with a reduced cost RAID system. BACKGROUND OF THE INVENTION [0002] A RAID based disk drive storage system as known in the art can employ numerous hard disk drives (“HDD”) in a RAID array, which can be the predominant failing component in the system in view of a failure rate of the numerous hard disk drives. As such, upon detecting a failed HDD in the RAID array, data stored in the failed HDD is migrated to a spare HDD whereby the spare HDD is rebuilt to match the failed HDD, and a repair service action is immediately initiated to facilitate a continued availability of the system. The cost associated with the serving each failed HDD in the RAID array, and a potential disruption to the users of the system has proven to be unacceptable in most cases. The computer industry is therefore continually striving to maximize the availability of the system to the users while minimizing the cost and disruption of repair services. SUMMARY OF THE INVENTION [0003] One form of the present invention is a method of operating a storage controller in managing a storage system including a primary storage array having a plurality of primary storage units and a spare storage pool having one or more spare storage units. The method involves a testing by the storage controller of at least one repair service threshold representative of one or more operational conditions indicative of a necessity to repair at least one of the primary storage array and the spare storage unit, and a selective initiation by the storage controller of a repair service action for repairing one of the primary storage array and the spare storage unit based on the testing of the at least one repair service threshold. [0004] A second form of the present invention is a signal bearing medium tangibly embodying a program of machine-readable instructions executable by a processor to perform operations for operating a storage controller in managing a storage system including a primary storage array having a plurality of primary storage units and a spare storage pool having one or more spare storage units. The operations encompass a testing by the storage controller of at least one repair service threshold representative of one or more operational conditions indicative of a necessity to repair at least one of the primary storage array and the spare storage unit, and a selective initiation by the storage controller of a repair service action for repairing one of the primary storage array and the spare storage unit based on the testing of the at least one repair service threshold. [0005] A third form of the present invention is controller employing a processor and memory storing instructions operable with the processor for operating the storage controller in managing a storage system including a primary storage array having a plurality of primary storage units and a spare storage pool having one or more spare storage units. The instructions encompass a testing by the storage controller of at least one repair service threshold representative of one or more operational conditions indicative of a necessity to repair at least one of the primary storage array and the spare storage unit, and a selective initiation by the storage controller of a repair service action for repairing one of the primary storage array and the spare storage unit based on the testing of the at least one repair service threshold. [0006] A fourth form of the present invention is storage system employing a storage controller interfaced with a primary storage array having a plurality of primary storage units and a spare storage pool having one or more spare storage units. The storage controller tests at least one repair service threshold representative of one or more operational conditions indicative of a necessity to repair at least one of the primary storage array and the spare storage unit, and a selectively initiates a repair service action for repairing one of the primary storage array and the spare storage unit based on the testing of the at least one repair service threshold. [0007] The forgoing forms as well as other forms, objects and aspects as well as features and advantages of the present invention will become further apparent from the following detailed description of various embodiments of the present invention, read in conjunction with the accompanying drawings. The detailed description and drawings are merely illustrative of the present invention rather than limiting, the scope of the present invention being defined by the appended claims and equivalents thereof. BRIEF DESCRIPTION OF THE DRAWINGS [0008] FIG. 1 illustrates a storage controller, a primary storage array and a spare storage pool in accordance with the present invention; [0009] FIG. 2 illustrates a flow chart representative of one embodiment of a primary storage unit failure management method of the present invention; [0010] FIG. 3 illustrates exemplary embodiments of a primary storage array and a spare storage pool in accordance with the present invention prior to a failure of a primary storage unit in the primary storage array; [0011] FIG. 4 illustrates exemplary embodiments of a primary storage array and a spare storage pool in accordance with the present invention subsequent to a failure of a primary storage unit in the primary storage array involving a migration of data from the failed primary storage unit to a single spare storage unit; [0012] FIG. 5 illustrates exemplary embodiments of a primary storage array and a spare storage pool in accordance with the present invention subsequent to a failure of a primary storage unit in the primary storage array involving a migration of data from the failed primary storage unit to a pair of spare storage units; [0013] FIG. 6 illustrates a flow chart representative of one embodiment of repair service management method in accordance with the present invention; [0014] FIG. 7 illustrates a first embodiment of a RAID storage system in accordance with the present invention; [0015] FIG. 8 illustrates a second embodiment of a RAID storage system in accordance with the present invention; and [0016] FIG. 9 illustrates one embodiment of a network of distributed data processing systems in accordance with the present invention. DETAILED DESCRIPTION OF THE PRESENT INVENTION [0017] FIG. 1 illustrates a storage controller 10, a primary storage array 20, and a spare storage pool 30 of the present invention. [0018] Storage controller 10 employs one or more conventional processors 10, one or more conventional memories 11, a failure detection module 13, a data migration module 14 and a service notification module 15 to implement various storage management methods of the present invention as will be subsequently herein in connection with FIGS. 2 and 6. To this end, modules 13-15 are implemented in hardware, software stored in memories 11, firmware, or any mixture as would to occur to those having ordinary skill in the art. [0019] Primary storage array 20 (e.g., a RAID array) employs an X number of primary storage units 20(1)-20(X), where X≧2. Primary storage units 20(1)-20(X) can be in the form of any type of conventional memory (e.g., any type of disk drive). [0020] Spare storage pool 30 employs an Y number of spare storage units 30(1)-20(Y), where Y≧1. Spare storage units 30(1)-30(Y) also can be in the form of any type of conventional memory (e.g., any type of disk drive). Additionally, the form of primary storage units 20(1)-20(X) and the form of spare storage units 30(1)-30(X) can be identical or dissimilar. Furthermore, the operational characteristics of the primary storage units 20(1)-20(X) and the operational characteristics of the spare storage units 30(1)-30(X) can be identical or dissimilar. The operational characteristics of the units can include, but are not limited to, storage capacity, revolutions per minute, and an interface data rate. [0021] In practice, various conventional network technologies as would occur to those having ordinary skill in the art can be implemented to interface storage controller 10, primary storage array 20, and spare storage pool 30 in any one of a variety of conventional network topologies. Upon a formation of a storage network employing a particular interfacing of storage controller 10, primary storage array 20, and spare storage pool 30, a primary storage unit failure management method as represented by a flowchart 40 illustrated in FIG. 2 and a repair service management method as represented by a flowchart 50 illustrated in FIG. 6 can be executed to derive various advantages and benefits of the present invention. To this end, controller 10 contains information defining the size and form of primary storage array 20, the pertinent operational characteristics each primary storage unit 20(1)-20(X), the size and form of spare storage pool 30, and the operational characteristics of each spare storage unit 30(1)-30(X). [0022] Referring to FIG. 2, a stage S42 of flowchart 40 involves a conventional determination by controller 10 (FIG. 1) via module 13 (FIG. 1) as to whether a primary storage unit 20(1)-20(X) (FIG. 1) has failed (e.g., a read failure or a write failure). Controller 10 will loop this decision stage S42 until such time a failure by one of the primary storage units 20(1)-20(X) has been detected by controller 10, which thereafter sequentially proceeds to a stage S44 and a stage S46 of flowchart 40. Stage S44 involves a conventional migration by controller 10 via module 14 of data stored in the failed primary storage unit to one or more functional spare storage units in dependence upon a size of the data to be migrated relative to the storage capacities of the spare storage units. Stage S46 involves a redefining of primary storage array 20 and spare storage pool 30 by controller 10. [0023] To facilitate an understanding of stages S44 and S46, FIG. 3 illustrates a RAID primary storage array 21 as one form of primary storage array 20 (FIG. 1) having six (6) primary storage units P1-P6 and a spare storage pool 31 as one form of spare storage pool 30 (FIG. 1) having six (6) spare storage units S1-S6. In one example of stages S44 and S46, data from a failed primary storage unit P6 is conventionally migrated by controller 10 via module 14 to a spare storage unit S6 as illustrated in FIG. 4 whereby primary storage array 21 is redefined to a primary storage array 21′ including primary storage units P1-P6 and spare storage unit S6, and spare storage pool 31 is redefined to a spare storage pool 31′ including spare storage units S1-S5. In one example of stages S44 and S46, data from a failed primary storage unit P6 is conventionally migrated by controller 10 via module 14 to spare storage units S5 and S6 as illustrated in FIG. 5 whereby primary storage array 21 is redefined to a primary storage array 21″ including primary storage units P1-P6 and spare storage units S5 and S6, and spare storage pool 31 is redefined to a spare storage pool 31″ including spare storage units S1-S4. For both examples, primary storage unit P6 is deemed non-functional by controller 10 whereby any subsequent physical or logical addressing of primary storage unit P6 is directed to spare storage units containing the data migrated from primary storage unit P6. [0024] Flowchart 40 returns to stage S42 upon a completion of stage S46. The return to stage S42 can be immediately, subsequent to an elapse of a particular time period, subsequent to an occurrence of one or more events, or any other facts deemed necessary to ensure an acceptable return to stage S42. [0025] Referring to FIG. 6, an execution of flowchart 50 is initiated on a periodic basis or sporadic basis until such time stage S44 has been invoked due to a detection of a failed primary storage unit. Irrespective of how the execution of flowchart 50 is initiated, a stage S52 of flowchart 50 involves a testing by controller 10 (FIG. 1) via module 15 (FIG. 1) of one or more repair service thresholds representative of operational conditions indicative of a necessity to repair (i.e., fix or replace) a primary storage array 20 (FIG. 1) and/or spare storage pool 30 (FIG. 1). In practice, a number and/or diversity of the repair service threshold(s) are dependent upon a commercial implementation of the present invention, and therefore are without limit. In one embodiment, the repair service thresholds are derived from (1) a comparison of one or more operational characteristics of the primary storage array and the spare storage pool, (2) an operational status of the primary storage array, and/or (3) an operational status of the spare storage pool. [0026] To facilitate a further understanding of stage S52, the following TABLE 1 lists exemplary repair service thresholds in the context of an occurrence of a migration of data from failed primary storage unit P6 to a functional spare storage unit S6 as illustrated in FIG. 4: TABLE 1 NO. REPAIR SERVICE THRESHOLDS TRUE 1 A revolutions per minute of spare storage unit S6 is Y/N lower than a revolutions per minute of primary storage unit P6 2 An interface data rate of spare storage unit S6 is less than Y/N a storage capacity of primary storage unit P6 3 Spare storage unit S6 and one of primary storage units Y/N P1-P5 constitute a mirrored pair on the same device interface 4 There are less than two (2) spare storage units among Y/N units S1-S4 with a storage capacity equal to or greater than a storage capacity of primary storage units P1-P5 5 There are less than two (2) spare storage units among Y/N units S1-S4 that are attached to the same interface 6 A repair action is required for a non-failure condition of Y/N the primary storage array, and there is at least one in- operative spare storage units among units S1-S4 [0027] Referring again to FIG. 2, a stage S54 of flowchart 50 involves a determination by controller 10 via module 15 as to whether a repair service is warranted based on the repair service thresholds tested during stage S52. In one embodiment, controller 10 implements a logical scheme during stage S52 to facilitate a determination by controller 10 as to whether a repair service is warranted based on the repair service thresholds tested during stage S52. For example, controller 10 can implement a logic OR operation of thresholds 1-6 listed in TABLE 1 whereby controller 10 determines a repair service is warranted if at least one of the repair service thresholds is deemed to be TRUE by controller 10 during stage S52. Also by example, controller 10 can implement a logic AND operation of thresholds 1-6 listed in TABLE 1 whereby controller 10 determines a repair service is warranted if and only if all of the repair service thresholds are deemed to be TRUE by controller 10 during stage S52. [0028] Flowchart 50 is terminated by controller 10 upon controller 10 determining a repair service is not warranted during stage S54. Otherwise, a stage S56 of flowchart 50 involves a testing by controller 10 (FIG. 1) via module 15 (FIG. 1) of one or more copy back thresholds representative of operational conditions indicative of a necessity to copy back data from the migrated spare storage unit(s) to a repaired primary storage unit. In practice, a number and/or diversity of the copy back threshold(s) are dependent upon a commercial implementation of the present invention, and therefore are without limit. In one embodiment, the copy back thresholds are derived from (1) a comparison of one or more operational characteristics of the primary storage array and the spare storage pool, (2) an operational status of the primary storage array, and/or (3) an operational status of the spare storage pool. [0029] To facilitate a further understanding of stage S52, the following TABLE 2 lists exemplary copy back thresholds 1-6 in the context of an occurrence of a migration of data from failed primary storage unit P6 to a functional spare storage unit S6 as illustrated in FIG. 4: TABLE 2 NO. COPY BACK THRESHOLDS TRUE 1 A storage capacity of spare storage unit S6 is lower than Y/N a storage capacity of primary storage unit P6 2 A revolutions per minute of spare storage unit S6 is Y/N lower than a revolutions per minute of primary storage unit P6 3 A revolutions per minute of spare storage unit S6 is Y/N greater than a revolutions per minute of primary storage unit P6 4 An interface data rate of spare storage unit S6 is less Y/N than a storage capacity of primary storage unit P6 5 An interface data rate of spare storage unit S6 is greater Y/N than a storage capacity of primary storage unit P6 6 Spare storage unit S6 and one of primary storage units Y/N P1-P5 constitute a mirrored pair on the same device interface 7 An interface configuration of the primary storage array Y/N and/or spare storage pool is incorrect [0030] A stage S58 of flowchart 50 involves a determination by controller 10 via module 15 as to whether a copy back is warranted based on the copy back thresholds tested during stage S56. In one embodiment, controller 10 implements a logical scheme during stage S56 to facilitate a determination by controller 10 as to whether a copy back is warranted based on the copy back thresholds tested during stage S56. For example, controller 10 can implement a logic OR operation of thresholds 1-7 listed in TABLE 2 whereby controller 10 determines a copy back is warranted if at least one of the copy back thresholds is deemed to be TRUE by controller 10 during stage S56. Also by example, controller 10 can implement a logic AND operation of thresholds 1-7 listed in TABLE 3 whereby controller 10 determines a copy back is warranted if and only if all of the copy back thresholds 1-7 are deemed to be TRUE by controller 10 during stage S56. [0031] Upon a determination that a copy back is not warranted during state S58, controller 10 proceeds to a stage S60 of flowchart 50 to initiate a repair service action without a copy back. Conversely, upon a determination that a copy back is warranted during state S58, controller 10 proceeds to a stage S62 of flowchart 50 to initiate a repair service action with a copy back. [0032] In practice, the initiation of the repair service is dependent upon a commercial implementation of the present invention, and is therefore without limit. In one embodiment, controller 10 establishes a communication with a service center to thereby request a repair service visit whereby a repair person can repair (i.e., fix or replace) any failed storage disks, incorrect interface configurations, or any other problems associated with the primary storage array and/or the spare storage pool. As to the copy back, the request for repair service visit can indicate a need of a copy back and/or techniques on site can be implemented to indicate a copy back is needed (e.g., a beep, a lit LED, etc.) [0033] As previously described in connection with FIG. 1, various conventional network technologies as would occur to those having ordinary skill in the art can be implemented to interface storage controller 10, primary storage array 20, and spare storage pool 30 in any one of a variety of conventional network topologies. FIG. 7 is an exemplary illustration of a bus topology wherein storage controller 10 is interfaced via a bus 70 to a primary storage array 21 (FIG. 3) and spare storage pool 31 (FIG. 3). Storage controller 10 is further interfaced, directly or indirectly via a network, to a host computer 71 for issuing read and write requests to controller 10 and a service center 72 for responding to a repair service action initiated by controller 10. [0034] FIG. 8 is an exemplary illustration of a fibre channel arbitrated loop (“FCAL”) system wherein storage controller 10 is integrated into a pair of servers 80 and 81, which are interfaced via 10 adapter cards (not shown) and a fiber channel arbitrated loop connections 83 and 84 to a primary storage array 22 and spare storage pool 32. [0035] The present invention could be implemented on a variety of hardware platforms. FIG. 9 depicts a distributed data processing network 90 employing a network 91, which is the media used to provide communications links between various devices and computers connected together within distributed data processing network 90. Network 91 may include permanent connections, such as wire or fiber optic cables, or temporary connections made through telephone or wireless communications. [0036] In the depicted example, a pair of RAID systems 92 and 93, a pair of conventional a service centers 94 and 95, and a pair of conventional clients 96 and 97 are connected to network 91. Storage system 92 and Storage system 93 represent a Storage system in accordance with the present invention, such as, for example, a RAID system including storage controller 10, a primary storage array 20 and a spare storage pool 30 as illustrated in FIG. 1. Service centers 94 and 95, and clients 96 and 97 represent a variety of conventional computing devices, such as mainframes, personal computers, personal digital assistants (PDAs), etc. Distributed data processing network 90 may include more or less Storage systems, servers and clients as shown as well as additional networks, routers, and other devices as would occur to those having ordinary skill in the art. [0037] Distributed data processing network 90 may include the Internet with network 91 representing a worldwide collection of networks and gateways that use the TCP/IP suite of protocols to communicate with one another. Of course, distributed data processing network 130 may also include a number of different types of networks, such as, for example, an intranet, a local area network (LAN), or a wide area network (WAN). [0038] FIG. 9 is intended as an example of a heterogeneous computing environment and not as an architectural limitation for the present invention. While the embodiments of the present invention disclosed herein are presently considered to be preferred embodiments, various changes and modifications can be made without departing from the spirit and scope of the present invention. The scope of the invention is indicated in the appended claims, and all changes that come within the meaning and range of equivalents are intended to be embraced therein. Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5077736 *Feb 13, 1990Dec 31, 1991Storage Technology CorporationDisk drive memoryUS5155835 *Nov 19, 1990Oct 13, 1992Storage Technology CorporationMultilevel, hierarchical, dynamically mapped data storage subsystemUS5351246 *Jan 3, 1994Sep 27, 1994International Business Machines CorporationMethod and means for coding and rebuilding that data contents of unavailable DASDs or rebuilding the contents of DASDs in error in the presence of reduced number of unavailable DASDs in a DASD arrayUS5430855 *Aug 31, 1994Jul 4, 1995Storage Technology CorporationDisk drive array memory system using nonuniform disk drivesUS6282670 *Jun 22, 1998Aug 28, 2001International Business Machines CorporationManaging defective media in a RAID systemUS6598174 *Apr 26, 2000Jul 22, 2003Dell Products L.P.Method and apparatus for storage unit replacement in non-redundant arrayUS6751758 *Jun 20, 2001Jun 15, 2004Emc CorporationMethod and system for handling errors in a data storage environmentUS7028216 *Feb 23, 2004Apr 11, 2006Hitachi, Ltd.Disk array system and a method of avoiding failure of the disk array systemUS7313721 *Aug 4, 2004Dec 25, 2007Dot Hill Systems CorporationApparatus and method for performing a preemptive reconstruct of a fault-tolerant RAID arrayUS20010044879 *Feb 13, 2001Nov 22, 2001Moulton Gregory HaganSystem and method for distributed management of data storageUS20020162057 *Apr 30, 2001Oct 31, 2002Talagala Nisha D.Data integrity monitoring storage systemUS20030188097 *Mar 29, 2002Oct 2, 2003Holland Mark C.Data file migration from a mirrored RAID to a non-mirrored XOR-based RAID without rewriting the dataUS20070220313 *Apr 14, 2006Sep 20, 2007Hitachi, Ltd.Storage control device and data recovery method for storage control device* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS7308600 *Aug 11, 2004Dec 11, 2007International Business Machines CorporationManaging access to spare data storage devicesUS7464290 *Dec 29, 2005Dec 9, 2008Promise Technology, Inc.Data storage system and managing method thereofUS7523350May 27, 2005Apr 21, 2009Dot Hill Systems CorporationTimer-based apparatus and method for fault-tolerant booting of a storage controllerUS7673167 *Mar 2, 2010International Business Machines CorporationRAID array data member copy offload in high density packagingUS7685463 *Jun 23, 2006Mar 23, 2010Emc CorporationDisk drive management systemUS7711989 *Apr 11, 2006May 4, 2010Dot Hill Systems CorporationStorage system with automatic redundant code component failure detection, notification, and repairUS7877554 *Apr 19, 2006Jan 25, 2011Oracle America, Inc.Method and system for block reallocationUS7895467 *Feb 22, 2011Hitachi, Ltd.Storage control system and storage control methodUS7941628May 10, 2011International Business Machines CorporationAllocation of heterogeneous storage devices to spares and storage arraysUS8020032Sep 13, 2011International Business Machines CorporationMethod for providing deferred maintenance on storage subsystemsUS8201019 *Apr 28, 2009Jun 12, 2012International Business Machines CorporationData storage device in-situ self test, repair, and recoveryUS8281090 *Oct 9, 2006Oct 2, 2012Infortrend Technology, Inc.Pool spares for data storage virtualization subsystemUS8327184Jan 26, 2011Dec 4, 2012Hitachi, Ltd.Storage control system and storage control methodUS8825974Aug 30, 2012Sep 2, 2014Infortrend Technology, Inc.Pool spares for data storage virtualization subsystemUS9053114Aug 7, 2014Jun 9, 2015Igneous Systems, Inc.Extensible data pathUS9075773May 7, 2014Jul 7, 2015Igneous Systems, Inc.Prioritized repair of data storage failuresUS9098451 *Nov 21, 2014Aug 4, 2015Igneous Systems, Inc.Shingled repair set for writing dataUS9110607Jul 25, 2014Aug 18, 2015Infortrend Technology, Inc.Pool spares for data storage virtualization subsystemUS9201735Jun 25, 2014Dec 1, 2015Igneous Systems, Inc.Distributed storage data repair air via partial data rebuild within an execution pathUS9276900Mar 19, 2015Mar 1, 2016Igneous Systems, Inc.Network bootstrapping for a distributed storage systemUS9305666Jul 6, 2015Apr 5, 2016Igneous Systems, Inc.Prioritized repair of data storage failuresUS20060036903 *Aug 11, 2004Feb 16, 2006Dubal Kamlesh IManaging access to spare data storage devicesUS20060236150 *May 27, 2005Oct 19, 2006Dot Hill Systems CorporationTimer-based apparatus and method for fault-tolerant booting of a storage controllerUS20060236198 *Apr 11, 2006Oct 19, 2006Dot Hill Systems CorporationStorage system with automatic redundant code component failure detection, notification, and repairUS20060245103 *Jun 28, 2005Nov 2, 2006Koichi UenoStorage device system operating based on system information, and method for controlling thereofUS20060271818 *Dec 29, 2005Nov 30, 2006Promise Technology, Inc.Data storage system and managing method thereofUS20070078794 *Oct 9, 2006Apr 5, 2007Infortrend Technology, Inc.Pool spares for data storage virtualization subsystemUS20070106870 *Apr 19, 2006May 10, 2007Sun Microsystems, Inc.Method and system for block reallocationUS20080189723 *Feb 6, 2007Aug 7, 2008International Business Machines CorporationRAID Array Data Member Copy Offload in High Density PackagingUS20090031167 *Jan 11, 2008Jan 29, 2009Hitachi, Ltd.Storage control system and storage control methodUS20090063768 *Sep 4, 2007Mar 5, 2009International Business Machines CorporationAllocation of heterogeneous storage devices to spares and storage arraysUS20090172468 *Dec 27, 2007Jul 2, 2009International Business Machines CorporationMethod for providing deferred maintenance on storage subsystemsUS20100275057 *Oct 28, 2010International Business Machines CorporationData Storage Device In-Situ Self Test, Repair, and RecoveryUS20110119527 *May 19, 2011Hitachi, Ltd.Storage control system and storage control methodUS20150100821 *Aug 13, 2014Apr 9, 2015Fujitsu LimitedStorage control apparatus, storage control system, and storage control methodUS20150205667 *Jan 23, 2014Jul 23, 2015DSSD, Inc.Method and system for service-aware data placement in a storage systemUS20160070628 *Sep 9, 2014Mar 10, 2016Dell Products, LpMember Replacement in an Array of Information Storage Devices* Cited by examinerClassifications U.S. Classification714/6.32, 714/E11.085International ClassificationG06F11/00Cooperative ClassificationG06F2201/81, G06F11/2094, G06F11/1662European ClassificationG06F11/20S6Legal EventsDateCodeEventDescriptionJul 15, 2004ASAssignmentOwner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW YFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:VAN GUNDY, STEVEN R.;BENHASE, MICHAEL T.;KRAEMER, BRIAN C.;AND OTHERS;REEL/FRAME:015626/0074;SIGNING DATES FROM 20040526 TO 20040708Dec 24, 2012REMIMaintenance fee reminder mailedApr 18, 2013FPAYFee paymentYear of fee payment: 4Apr 18, 2013SULPSurcharge for late paymentRotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services