US7472223B1 - Surface level sparing in disk drives - Google Patents
Surface level sparing in disk drives Download PDFInfo
- Publication number
- US7472223B1 US7472223B1 US11/529,143 US52914306A US7472223B1 US 7472223 B1 US7472223 B1 US 7472223B1 US 52914306 A US52914306 A US 52914306A US 7472223 B1 US7472223 B1 US 7472223B1
- Authority
- US
- United States
- Prior art keywords
- hard disk
- disk platter
- identifier
- platter
- real
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active, expires
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/1658—Data re-synchronization of a redundant component, or initial sync of replacement, additional or spare unit
- G06F11/1662—Data re-synchronization of a redundant component, or initial sync of replacement, additional or spare unit the resynchronized component or unit being a persistent storage device
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
- G06F11/2094—Redundant storage or storage space
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
- G11B20/00—Signal processing not specific to the method of recording or reproducing; Circuits therefor
- G11B20/10—Digital recording or reproducing
- G11B20/18—Error detection or correction; Testing, e.g. of drop-outs
- G11B20/1883—Methods for assignment of alternate areas for defective areas
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
- G11B2220/00—Record carriers by type
- G11B2220/20—Disc-shaped record carriers
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
- G11B2220/00—Record carriers by type
- G11B2220/20—Disc-shaped record carriers
- G11B2220/25—Disc-shaped record carriers characterised in that the disc is based on a specific recording technology
- G11B2220/2508—Magnetic discs
- G11B2220/2516—Hard disks
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
- G11B2220/00—Record carriers by type
- G11B2220/40—Combinations of multiple record carriers
- G11B2220/41—Flat as opposed to hierarchical combination, e.g. library of tapes or discs, CD changer, or groups of record carriers that together store one title
- G11B2220/415—Redundant array of inexpensive disks [RAID] systems
Definitions
- a typical data storage system includes storage control circuitry (e.g., a front-end server, a storage processor, a set of directors, etc.) and hard disk drives.
- the storage control circuitry performs a variety of data storage operations (e.g., load and store operations) on behalf of one or more external clients by sending hard drive commands to the hard disk drives.
- a typical command uses an LBA (Logical Block Address) addressing mode in which the command specifies a starting LBA and a count.
- LBA Logical Block Address
- a typical hard disk drive includes multiple hard disk platters mounted to a common spindle. Each hard disk platter defines a top surface and a bottom surface for storing data in a non-volatile manner.
- the hard disk drive further includes a disk drive controller and, for each platter surface, a read head and a write head which are controlled by the disk drive controller to respectively read data from and write data to that platter surface.
- a data storage system In addition to the disk drives that regularly maintain data, it is common practice for a data storage system to include a hot spare disk drive.
- the hot spare disk drive kicks in by taking over the role of the failing disk drive. That is, the storage control circuitry stores a copy of the data that currently exists on the failing disk drive onto the hot spare disk drive. The storage control circuitry then operates the hot spare disk drive in place of the failing disk drive. Typically, the failing disk drive is then removed from the data storage system and discarded by a technician.
- an improved technique involves providing access to platter surfaces using surface virtualization.
- a mapping function is capable of mapping virtual platter surfaces to real platter surfaces (or alternatively virtual disk drive heads to real disk drive heads). Accordingly, from the perspective of a host, disk accesses can be carried out by addressing LBAs which translate to virtual platter surfaces. If there is a failure of a particular real platter surface, the mapping function can simply re-map the virtual platter surface to a new real platter surface without changing any addressing at the host (i.e., mapping of LBAs to virtual platter surfaces by the host can remain intact). Such a technique enables efficient surface-level sparing inside a disk drive.
- One embodiment is directed to a method of accessing a hard disk platter surface using surface virtualization.
- the method includes receiving a command to access a hard disk platter surface.
- the command specifies an address (e.g., a Logical Block Address).
- the method further includes providing a virtual surface identifier based on the address specified by the command, and generating a particular real surface identifier based on the virtual surface identifier.
- the particular real surface identifier corresponds to a particular hard disk platter surface among multiple hard disk platter surfaces of a set of disk drives.
- the method further includes accessing the particular hard disk platter surface among the multiple hard disk platter surfaces of the set of disk drives based on the particular real surface identifier.
- Such operation is capable of being carried out within a disk drive controller in a manner that is transparent to a host, or alternatively by the host.
- FIG. 1 is a block diagram of a data storage system which performs data storage operations using hard disk platter surface virtualization.
- FIG. 2 is a block diagram of a mapping table which illustrates a mapping function performed by the data storage system of FIG. 1 for surface virtualization.
- FIG. 3 is a block diagram of a set of hard disk platters and a current mapping state of platter surfaces in accordance with the mapping table of FIG. 2 .
- FIG. 4 is a layer diagram illustrating operation of a disk drive controller at various levels when carrying out surface virtualization.
- FIG. 5 is a general flow diagram illustrating a fault handling procedure of the data storage system of when responding to a failure of a hard disk platter surface (or a head to that hard disk platter surface).
- FIG. 6 is a block diagram of the set of hard disk platters of FIG. 3 after the fault handling procedure.
- FIG. 7 is a block diagram of the mapping table when updated by the fault handling procedure of FIG. 5 .
- FIG. 8 is a block diagram of the mapping table illustrating operation of the fault handling procedure when the fault handling procedure is carried out by a host of the data storage system to enable utilization of a hot spare hard disk platter by multiple disk drives.
- a mapping function is capable of mapping virtual platter surfaces to real platter surfaces (or alternatively virtual disk drive heads to real disk drive heads). Accordingly, from the perspective of a host, disk accesses can be carried out by addressing LBAs which translate to virtual platter surfaces. If there is a failure of a particular real platter surface, the mapping function can simply re-map the virtual platter surface to a new real platter surface without changing any addressing at the host (i.e., mapping of LBAs to virtual platter surfaces by the host can remain intact). Such a technique enables efficient surface-level sparing inside a disk drive.
- FIG. 1 is a block diagram of a data storage system 20 which performs data storage operations using hard disk platter surface virtualization.
- the data storage system 20 includes a host 22 and a set of disk drives 24 ( 1 ), . . . , 24 ( n ) (i.e., one or more disk drives 24 ) coupled to the host 22 .
- Each disk drive 24 includes electronic circuitry 26 and multiple hard disk platters 28 (or disks) which rotate on a common spindle.
- the electronic circuitry 26 of each disk drive 24 includes a host interface 30 , a disk drive controller 32 and a platter interface 34 (see the disk drive 24 ( 1 ) in FIG. 1 ).
- the host 22 sends commands 36 to the disk drives 24 to perform a variety of data storage operations on behalf of one or more client devices.
- the disk drive controllers 32 receive the commands 36 through the host interfaces 30 and effectuate loading of data from and storing of data to the platters 28 through the platter interfaces 34 (i.e., read and write heads).
- Such operation is carried out using virtualization of the platter surfaces. That is, the commands 36 address blocks of data using LBAs (Logical Block Addresses) which translate into virtual platter surfaces rather than real platter surfaces.
- the disk drive controllers 32 then perform mapping functions to translate the virtual platter surfaces into real platter surfaces. Accordingly, if there is a failure of a real platter surface (e.g., a failure of a read head or a write head to that platter surface) within a disk drive 24 , the disk drive 24 can simply replace the failing platter surface with a spare platter surface and update the mapping so that the virtual platter surface now maps to the spare platter surface. As a result, there is no need to change the LBAs used by the host 22 . Furthermore, there is no need to discard the disk drive having the failed platter surface. Rather, the remaining real platter surfaces of that disk drive are still available for use. As such, the disk drive 24 can continue to operate with simple re-mapping and discontinued use of the failed platter surface. Further details will now be provided with reference to FIGS. 2 and 3
- FIGS. 2 and 3 illustrate how surface virtualization is carried out by a disk drive 24 .
- FIG. 2 is a block diagram of a mapping table 50 having multiple entries 52 which enable the disk drive controller 32 of the disk drive 24 to perform a mapping function for surface virtualization.
- FIG. 3 is a block diagram of the hard disk platters 28 of the disk drive 24 and the current mapping state as defined by the mapping table 50 .
- each entry 52 of the mapping table 50 includes an entry number field 54 , a virtual surface identifier field 56 and a real surface identifier field 58 .
- the entry number field 54 of each entry 52 is configured to store a unique entry number.
- the virtual surface identifier field 56 is configured to store an identifier which identifies a particular virtual platter surface 60 of the disk drive 24 .
- the real surface identifier field 58 is configured to store an identifier which identifies a particular real platter surface 62 of the disk drive 24 .
- each entry 52 identifies a relationship 64 between a virtual platter surface 60 as perceived by the host 22 and a real platter surface 62 of the disk drive 24 .
- Each platter 28 includes a top real platter surface 62 (T) and a bottom real platter surface 62 (B). Each real platter surface 62 is accessible via a read head and a write head which are illustrated by the reference numeral 66 in FIG. 3 (also see the platter interface 34 in FIG. 1 ).
- the first entry 52 of the mapping table 50 maps virtual platter surface “VS 1 ” to real platter surface “RS 1 ”.
- the second entry 52 maps virtual platter surface “VS 2 ” to real platter surface “RS 2 ”, and so on.
- the disk drive 24 includes three platters 28 which rotate about a spindle 68 . Accordingly, the three platters 28 of the disk drive 24 provide a total of six real platter surfaces.
- the disk drives 24 are capable of having a number of real platters 28 which is different from three (e.g., two, four, five, etc.).
- the entry number field 54 of the mapping table 50 is optional and the entries 52 (or their locations within the table 50 ) simply correspond to virtual surface identifiers (e.g., the first entry 52 corresponds to “VS 1 ”, the second entry 52 corresponds to “VS 2 ”, and so on). Further details will now be provided with reference to FIG. 4 in combination with FIGS. 1 through 3 .
- FIG. 4 is a layer diagram 80 illustrating the layered operation of the disk drive controller 32 at various levels when carrying out surface virtualization.
- the disk drive controller 32 obtains virtual surface identifiers based on LBAs of hard drive commands 36 which are received from the host 22 through the host interface 30 (also see FIG. 1 ).
- the disk drive controller 32 identifies the virtual platter surfaces 60 ( FIG. 3 ) containing data blocks to be accessed by the commands 36 .
- the host 22 wishes to access data on virtual surface “VS 1 ”
- the host 22 sends the disk drive 24 a command 36 having an LBA which layer 82 of the disk drive controller 32 translates into “VS 1 ”.
- the layer 82 of the disk drive controller 32 provides the virtual surface identifier “VS 1 ” which is then processed by the disk drive controller 32 at the next layer 84 .
- the disk drive controller 32 converts virtual surface identifiers corresponding to virtual platter surfaces 60 into real surface identifiers which correspond to real platter surfaces 62 ( FIG. 3 ).
- the layer 84 of the disk drive controller 32 obtains the virtual surface identifiers from the layer 82 and applies a mapping function to generate real surface identifiers from virtual surface identifiers.
- the disk drive controller 32 searches virtual surface identifier field 56 of the entries 52 of the mapping table 50 for “VS 1 ” ( FIG. 2 ). Such a function is capable of being carried out by applying a standard search algorithm or other hashing technique.
- layer 84 of the disk drive controller 32 finds that the first entry (i.e., entry “ 1 ”) includes the virtual surface identifier “VS 1 ” outputs “RS 1 ” as the real surface identifier which maps to the virtual surface identifier “VS 1 ”.
- the disk drive controller 32 simply indexes the mapping table 50 . That is, to find the real surface identifier corresponding to the first virtual surface identifier “VS 1 ”, the disk controller 32 accesses the first entry 52 in the table 50 . Similarly, to find the real surface identifier corresponding to the second virtual surface identifier “VS 2 ”, the disk controller 32 accesses the second entry 52 in the table 50 , and so on.
- the disk drive controller 32 accesses real platter surfaces 62 of the hard disk platters 28 based on the real surface identifiers from the layer 84 .
- the disk drive controller 32 accesses the real platter surface 62 corresponding to the real surface identifier “RS 1 ” ( FIG. 3 ).
- surface virtualization enables one or more real hard disk platter surfaces 62 to be keep as one or more hot spare platter surfaces 62 (S). That is, such hot spare real platter surfaces 62 (S) are not used to store data in the normal course of operation. Rather, such hot spare real platter surfaces 62 (S) are used to replace real platter surfaces 62 that fail during the normal course of operation. Further details along these lines will now be provided with reference back to FIGS. 2 and 3 .
- mapping table 50 maps a virtual surface identifier to the real surface identifier “RS 6 ” because the real surface identifier “RS 6 ” corresponds to a hot spare real platter surface 62 (S).
- the bottom-most real platter surface 60 is labeled as a hot spare real platter surface 62 (S) and thus is not used to store data in the normal course of operation. Rather, the real platter surface 62 (S) is kept by the disk drive 24 for hot replacement. Accordingly, no mapping of a virtual platter surface 60 to the real platter surface 62 (S) currently exists.
- FIGS. 5 through 7 illustrate how surface virtualization enables a disk drive 24 to replace a failing platter surface 62 with a hot spare platter surface 62 (S).
- FIG. 5 is a general flow diagram illustrating a fault handling procedure 100 when responding to a failure of a hard disk platter surface 62 (or a head to that hard disk platter surface 62 ) used during normal operation of the data storage system 20 .
- FIG. 6 is a block diagram of the hard disk platters 28 of the disk drive 24 showing a new state which is different than the previous state of FIG. 3 .
- FIG. 7 is a block diagram of the mapping table 50 which is modified to reflect the new state of FIG. 6 .
- the disk drive 24 has an initial state as that shown in FIG. 3 where the real platter surfaces 62 identified by the real surface identifiers RS 1 , . . . , RS 5 are used to store data during the normal course of operation, and that the real platter surface 62 identified by the real surface identifier RS 6 (i.e., the real platter surface 62 (S)) is kept as a hot spare.
- the real platter surface 62 identified by the real surface identifier RS 6 i.e., the real platter surface 62 (S)
- the real platter surface 62 (S) the real platter surface 62 (S)
- the disk drive controller 32 receives an indication of a failure corresponding to the real platter surface corresponding to the real surface identifier “RS 1 ”.
- the disk drive controller 32 may be unable to obtain a signal from a read head or a write head to that real surface 62 .
- the failure is illustrated in FIG. 6 with the “X” associated with the real surface identifier RS 1 .
- the disk drive controller 32 responds to the indication by placing a copy of the data, which is currently on the real platter surface 62 corresponding to the real surface identifier “RS 1 ”, onto the hot spare surface 62 (S).
- the disk drive controller 32 is capable of simply reading all of the data directly from the working read head and then storing the data on the hot spare surface 62 (S). This operation may occur entirely within the same disk drive 24 if both the failed real surface 62 and the spare surface 62 (S) reside within the same disk drive 24 . However, if the failed real surface 62 resides in one disk drive 24 and the spare surface 62 (S) resides in another disk drive 24 , this operation occurs across the disk drives 24 .
- the disk drive controller 32 is capable of rebuilding the data by reading one or more other real platter surfaces 62 and then storing the data on the hot spare surface 62 (S).
- the data on the failed real surface 62 can be rebuilt from data read from the non-failed real surfaces 62 of the disk drives 24 .
- the real platters 62 within a single disk drive 24 are configured to store data using such a distributed RAID scheme, the data can even be rebuilt entirely within the single disk drive 24 and then stored on a spare surface 62 (S) of that single disk drive 24 if such a spare surface 62 (S) is available within that single disk drive 24 .
- step 106 the disk drive controller 32 modifies the entry 52 (i.e., entry “ 1 ”) of the mapping table 50 to map the virtual surface identifier “VS 1 ” to the real surface identifier “RS 6 ” which corresponds to the hot spare surface 62 (S) ( FIG. 7 ).
- the disk drive controller 32 changes the contents of the real surface identifier field 58 of that entry 52 to now store the new surface identifier “RS 6 ”.
- This new relationship is illustrated in FIG. 6 as the reference line 108 which now points from the virtual platter surface 60 corresponding to virtual surface identifier “VS 1 ” to the real surface identifier “RS 6 ”.
- the host 22 does not need to change any LBAs in the commands 36 to the disk drive 24 and that replacement of the failed platter surface 62 with the hot spare platter surface 62 (S) can take place transparently to the host 22 . That is, the host 22 continues to use the same LBAs for any future access to the data since the host 22 still addresses the same virtual platter surfaces 60 . However, the disk drive controller 32 now maps the failed virtual platter surface 60 to the hot spare platter surface 62 (S) which has replaced the failed real platter surface 62 . Moreover, since the other real platter surfaces 62 of the disk drive 24 are still usable, there is no need to replace the entire disk drive 24 with an entire new hot spare disk drive 24 . Further details will now be provided with reference to FIG. 8 .
- FIG. 8 shows a block diagram of a mapping table 150 illustrating operation of the fault handling procedure 100 of FIG. 5 when surface virtualization is implemented across multiple disk drives 24 , i.e., disk drives 24 ( 1 ), . . . , 24 ( n ). That is, the fault handling procedure 100 of FIG. 5 does not need to be performed entirely within a disk drive controller 32 of a disk drive 24 as described above in connection with FIGS. 2 through 7 . Rather, the host 22 can obtain and maintain virtual and real platter surface details from the disk drives 24 through an application programming interface (API) which is supported by the disk drives 24 . By employing such an API, the host 22 is then capable of monitoring surface mapping and even building an aggregate mapping table for carrying out an aggregate mapping function as shown in FIG. 8 .
- API application programming interface
- entries “ 1 ” through “ 5 ” providing mapping of virtual surface identifiers “VS 1 _ 1 ”, . . . , “VS 1 _ 5 ” to real surface identifiers “RS 1 _ 1 ”, . . . , “RS 1 _ 5 ”, respectively, for a first disk drive 24 (e.g., the disk drive 24 ( 1 ) in FIG. 1 ).
- entries “ 6 ” through “ 11 ” providing mapping of virtual surface identifiers “VS 2 _ 1 ”, . . .
- the host 22 is configured to coordinate replacement of that real platter surface 62 with the hot spare surface 62 (S) by communicating with both the first and second disk drives 24 through the API to each disk drive 24 . Accordingly, the host 22 effectuates placement of the data which was originally on the failing real platter surface 62 within the second disk drive 24 onto the hot spare surface 62 (S) of the first disk drive 24 (e.g., by reading through a working read head to the failing real platter surface 62 , by rebuilding the data from RAID, etc.). As a result, the host 22 is now capable of accessing that data from the hot spare surface 62 (S) which now works in place of the failed real platter surface 62 corresponding to the real surface identifier “RS 2 _ 1 ”.
- a hot spare real platter surface 62 (S) is capable of operating as a hot spare to real platter surfaces 62 of other disk drives 24 of the data storage system 20 .
- Such operation alleviates the need for each disk drive 24 to provide a hot spare.
- the host 22 is not required to re-address the LBA address space.
- a mapping function is capable of mapping virtual platter surfaces 60 to real platter surfaces 62 (or alternatively virtual disk drive heads to real disk drive heads). Accordingly, from the perspective of a host 22 , disk accesses can be carried out by addressing LBAs which translate to virtual platter surfaces. If there is a failure of a particular real platter surface 62 , the mapping function can simply re-map the virtual platter surface 62 to a new real platter surface 62 (S) without changing any addressing at the host 22 (e.g., mapping of LBAs to virtual platter surfaces 60 by the host 22 can remain intact). Such a technique enables efficient surface-level sparing inside a disk drive 24 .
- the above-describe surface sparing techniques are capable of being carried out either within a disk drive controller 32 of a disk drive 24 or by a host 22 .
- the circuitry of the disk drive controller 32 is configured so that replacement of a failed real surface 62 within a disk drive 24 is carried out by the disk drive controller 32 of that disk drive 24 ; even if the data must be rebuilt, the rebuilding operation can be carried out by the disk drive controller 32 .
- the host 22 is configured to maintain the mapping table 50 (see FIG. 8 ) and then carry out the rebuilding operation using the API to the disk drives 24 .
- the same disk drives 24 which are configured to support surface sparing can be configured to carry out block sparing.
- the disk drive controller 32 maps a failed block on a particular real surface 62 to a spare block on that same real surface 62 .
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Signal Processing (AREA)
- Signal Processing For Digital Recording And Reproducing (AREA)
Abstract
Description
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/529,143 US7472223B1 (en) | 2006-09-28 | 2006-09-28 | Surface level sparing in disk drives |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/529,143 US7472223B1 (en) | 2006-09-28 | 2006-09-28 | Surface level sparing in disk drives |
Publications (1)
Publication Number | Publication Date |
---|---|
US7472223B1 true US7472223B1 (en) | 2008-12-30 |
Family
ID=40138579
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/529,143 Active 2027-06-08 US7472223B1 (en) | 2006-09-28 | 2006-09-28 | Surface level sparing in disk drives |
Country Status (1)
Country | Link |
---|---|
US (1) | US7472223B1 (en) |
Cited By (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080010500A1 (en) * | 2006-06-14 | 2008-01-10 | Fujitsu Limited | RAID controller, RAID system and control method for RAID controller |
US20120079317A1 (en) * | 2010-09-27 | 2012-03-29 | Chandrashekar Nelogal | System and method for information handling system redundant storage rebuild |
US20130088946A1 (en) * | 2011-10-06 | 2013-04-11 | Samsung Electronics Co., Ltd. | Method for playing back recording medium and recording medium playback device using the same |
US20130201809A1 (en) * | 2012-02-06 | 2013-08-08 | Hitachi Consumer Electronics Co., Ltd. | Recording/reproducing system and server |
US8612706B1 (en) | 2011-12-21 | 2013-12-17 | Western Digital Technologies, Inc. | Metadata recovery in a disk drive |
US8756361B1 (en) * | 2010-10-01 | 2014-06-17 | Western Digital Technologies, Inc. | Disk drive modifying metadata cached in a circular buffer when a write operation is aborted |
US8756382B1 (en) | 2011-06-30 | 2014-06-17 | Western Digital Technologies, Inc. | Method for file based shingled data storage utilizing multiple media types |
US8954664B1 (en) | 2010-10-01 | 2015-02-10 | Western Digital Technologies, Inc. | Writing metadata files on a disk |
US20150081991A1 (en) * | 2012-05-25 | 2015-03-19 | Fujitsu Limited | Information processing apparatus and access control method |
US9324359B2 (en) | 2012-03-30 | 2016-04-26 | Hitachi—LG Data Storage, Inc. | System and server for efficient data recording on and reproduction from storage media having multiple surfaces |
JP2019523490A (en) * | 2016-07-19 | 2019-08-22 | アール−ストール インコーポレイテッド | Method and apparatus for implementing non-aggregated memory platters |
US11099954B2 (en) * | 2018-10-31 | 2021-08-24 | EMC IP Holding Company LLC | Method, device, and computer program product for rebuilding data |
US20220334750A1 (en) * | 2020-01-06 | 2022-10-20 | Huawei Technologies Co., Ltd. | Data Access Method, Hard Disk, and Storage Device |
Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5216655A (en) | 1991-06-26 | 1993-06-01 | Digital Equipment Corporation | Method and apparatus for surface reallocation for improved manufacturing process margin |
US6526476B2 (en) | 1998-02-27 | 2003-02-25 | Stmicroelectronics N.V. | Defective data sector management system |
US6697958B1 (en) * | 1998-12-25 | 2004-02-24 | Sony Corporation | Method and apparatus for driving a recording medium, method and system for recording and reproducing information, and information supplying medium |
US6839802B2 (en) * | 2000-12-08 | 2005-01-04 | International Business Machines Corporation | Method, system, and program for writing files to zone formatted storage media to improve data transfer rates |
US20050114350A1 (en) | 2001-11-28 | 2005-05-26 | Interactive Content Engines, Llc. | Virtual file system |
US20050144517A1 (en) * | 2003-12-30 | 2005-06-30 | Matsushita Electric Industrial Co., Ltd. | Systems and methods for bypassing logical to physical address translation and maintaining data zone information in rotatable storage media |
US6925580B2 (en) * | 1999-12-03 | 2005-08-02 | Seagate Technology Llc | Full volume slip defect management in a disc drive |
US6947234B2 (en) | 2002-07-23 | 2005-09-20 | International Business Machines Corporation | Method, system, and program for performing error correction in a storage device having a magnetic storage medium |
US6978345B2 (en) | 2001-05-15 | 2005-12-20 | Hewlett-Packard Development Company, L.P. | Self-mirroring high performance disk drive |
US20060107131A1 (en) | 2004-11-02 | 2006-05-18 | Andy Mills | Multi-platter disk drive controller and methods for synchronous redundant data operations |
US7245445B2 (en) | 2002-11-25 | 2007-07-17 | Samsung Electronics Co., Ltd. | Method of managing defects in hard disk drive, recording media therefor and hard disk drive therefor |
-
2006
- 2006-09-28 US US11/529,143 patent/US7472223B1/en active Active
Patent Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5216655A (en) | 1991-06-26 | 1993-06-01 | Digital Equipment Corporation | Method and apparatus for surface reallocation for improved manufacturing process margin |
US6526476B2 (en) | 1998-02-27 | 2003-02-25 | Stmicroelectronics N.V. | Defective data sector management system |
US6697958B1 (en) * | 1998-12-25 | 2004-02-24 | Sony Corporation | Method and apparatus for driving a recording medium, method and system for recording and reproducing information, and information supplying medium |
US6925580B2 (en) * | 1999-12-03 | 2005-08-02 | Seagate Technology Llc | Full volume slip defect management in a disc drive |
US6839802B2 (en) * | 2000-12-08 | 2005-01-04 | International Business Machines Corporation | Method, system, and program for writing files to zone formatted storage media to improve data transfer rates |
US6978345B2 (en) | 2001-05-15 | 2005-12-20 | Hewlett-Packard Development Company, L.P. | Self-mirroring high performance disk drive |
US20050114350A1 (en) | 2001-11-28 | 2005-05-26 | Interactive Content Engines, Llc. | Virtual file system |
US6947234B2 (en) | 2002-07-23 | 2005-09-20 | International Business Machines Corporation | Method, system, and program for performing error correction in a storage device having a magnetic storage medium |
US7245445B2 (en) | 2002-11-25 | 2007-07-17 | Samsung Electronics Co., Ltd. | Method of managing defects in hard disk drive, recording media therefor and hard disk drive therefor |
US20050144517A1 (en) * | 2003-12-30 | 2005-06-30 | Matsushita Electric Industrial Co., Ltd. | Systems and methods for bypassing logical to physical address translation and maintaining data zone information in rotatable storage media |
US20060107131A1 (en) | 2004-11-02 | 2006-05-18 | Andy Mills | Multi-platter disk drive controller and methods for synchronous redundant data operations |
Cited By (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7587631B2 (en) * | 2006-06-14 | 2009-09-08 | Fujitsu Limited | RAID controller, RAID system and control method for RAID controller |
US20080010500A1 (en) * | 2006-06-14 | 2008-01-10 | Fujitsu Limited | RAID controller, RAID system and control method for RAID controller |
US20120079317A1 (en) * | 2010-09-27 | 2012-03-29 | Chandrashekar Nelogal | System and method for information handling system redundant storage rebuild |
US8726070B2 (en) * | 2010-09-27 | 2014-05-13 | Dell Products L.P. | System and method for information handling system redundant storage rebuild |
US8954664B1 (en) | 2010-10-01 | 2015-02-10 | Western Digital Technologies, Inc. | Writing metadata files on a disk |
US8756361B1 (en) * | 2010-10-01 | 2014-06-17 | Western Digital Technologies, Inc. | Disk drive modifying metadata cached in a circular buffer when a write operation is aborted |
US8756382B1 (en) | 2011-06-30 | 2014-06-17 | Western Digital Technologies, Inc. | Method for file based shingled data storage utilizing multiple media types |
US20130088946A1 (en) * | 2011-10-06 | 2013-04-11 | Samsung Electronics Co., Ltd. | Method for playing back recording medium and recording medium playback device using the same |
US8612706B1 (en) | 2011-12-21 | 2013-12-17 | Western Digital Technologies, Inc. | Metadata recovery in a disk drive |
US20130201809A1 (en) * | 2012-02-06 | 2013-08-08 | Hitachi Consumer Electronics Co., Ltd. | Recording/reproducing system and server |
CN103247306A (en) * | 2012-02-06 | 2013-08-14 | 日立乐金资料储存股份有限公司 | Recording/reproducing system and server |
CN103247306B (en) * | 2012-02-06 | 2016-04-06 | 日立乐金资料储存股份有限公司 | Recording/reproducing system, server |
US9311958B2 (en) * | 2012-02-06 | 2016-04-12 | Hitachi-Lg Data Storage, Inc. | Recording/reproducing system and server |
US9324359B2 (en) | 2012-03-30 | 2016-04-26 | Hitachi—LG Data Storage, Inc. | System and server for efficient data recording on and reproduction from storage media having multiple surfaces |
US20150081991A1 (en) * | 2012-05-25 | 2015-03-19 | Fujitsu Limited | Information processing apparatus and access control method |
US9734055B2 (en) * | 2012-05-25 | 2017-08-15 | Fujitsu Limited | Information processing apparatus and access control method |
JP2019523490A (en) * | 2016-07-19 | 2019-08-22 | アール−ストール インコーポレイテッド | Method and apparatus for implementing non-aggregated memory platters |
US11099954B2 (en) * | 2018-10-31 | 2021-08-24 | EMC IP Holding Company LLC | Method, device, and computer program product for rebuilding data |
US20220334750A1 (en) * | 2020-01-06 | 2022-10-20 | Huawei Technologies Co., Ltd. | Data Access Method, Hard Disk, and Storage Device |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7472223B1 (en) | Surface level sparing in disk drives | |
US8131969B2 (en) | Updating system configuration information | |
US9152332B2 (en) | Storage system and method for reducing energy consumption | |
TWI716416B (en) | Storage system, method and system for managing storage media, method of operating storage system, and non-transitory computer-readable medium | |
US8635424B2 (en) | Storage system and control method for the same | |
US9367265B2 (en) | Storage system and method for efficiently utilizing storage capacity within a storage system | |
US6877011B2 (en) | System and method for host based storage virtualization | |
JP6732684B2 (en) | Information processing device, storage device, and information processing system | |
US6941439B2 (en) | Computer system | |
US20070162692A1 (en) | Power controlled disk array system using log storage area | |
US9009405B2 (en) | Methods and systems for instantaneous online capacity expansion | |
US9026845B2 (en) | System and method for failure protection in a storage array | |
US20060195659A1 (en) | Method for managing volume groups considering storage tiers | |
US8645610B2 (en) | Organizing and managing a memory blade with super pages and buffers | |
US20120030406A1 (en) | Hypervisor-based management of local and remote virtual memory pages | |
US20090292870A1 (en) | Storage apparatus and control method thereof | |
US20060253674A1 (en) | Automatic disk healing | |
US10102138B2 (en) | Division of data storage in single-storage device architecture | |
JPH0683708A (en) | Method and device for storing data | |
KR102585883B1 (en) | Operating method of memory system and memory system | |
US20120233484A1 (en) | Method of, and apparatus for, power management in a storage resource | |
JP2007334533A (en) | Storage system | |
CN109558068B (en) | Data migration method and migration system | |
JPH09288547A (en) | Array-type storage device | |
US8510507B2 (en) | Data storage mirroring using virtual mirror |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: EMC CORPORATION, MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:OFER, ADI;REEL/FRAME:018356/0737 Effective date: 20060927 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
AS | Assignment |
Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT, TEXAS Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040136/0001 Effective date: 20160907 Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT, NORTH CAROLINA Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040134/0001 Effective date: 20160907 Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLAT Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040134/0001 Effective date: 20160907 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., A Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040136/0001 Effective date: 20160907 |
|
AS | Assignment |
Owner name: EMC IP HOLDING COMPANY LLC, MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:EMC CORPORATION;REEL/FRAME:040203/0001 Effective date: 20160906 |
|
AS | Assignment |
Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., T Free format text: SECURITY AGREEMENT;ASSIGNORS:CREDANT TECHNOLOGIES, INC.;DELL INTERNATIONAL L.L.C.;DELL MARKETING L.P.;AND OTHERS;REEL/FRAME:049452/0223 Effective date: 20190320 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., TEXAS Free format text: SECURITY AGREEMENT;ASSIGNORS:CREDANT TECHNOLOGIES, INC.;DELL INTERNATIONAL L.L.C.;DELL MARKETING L.P.;AND OTHERS;REEL/FRAME:049452/0223 Effective date: 20190320 |
|
AS | Assignment |
Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., TEXAS Free format text: SECURITY AGREEMENT;ASSIGNORS:CREDANT TECHNOLOGIES INC.;DELL INTERNATIONAL L.L.C.;DELL MARKETING L.P.;AND OTHERS;REEL/FRAME:053546/0001 Effective date: 20200409 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |
|
AS | Assignment |
Owner name: WYSE TECHNOLOGY L.L.C., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: SCALEIO LLC, MASSACHUSETTS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: MOZY, INC., WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: MAGINATICS LLC, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: FORCE10 NETWORKS, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: EMC IP HOLDING COMPANY LLC, TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: EMC CORPORATION, MASSACHUSETTS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL SYSTEMS CORPORATION, TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL SOFTWARE INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL MARKETING L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL INTERNATIONAL, L.L.C., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL USA L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: CREDANT TECHNOLOGIES, INC., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: AVENTAIL LLC, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: ASAP SOFTWARE EXPRESS, INC., ILLINOIS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 |
|
AS | Assignment |
Owner name: SCALEIO LLC, MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC), MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL INTERNATIONAL L.L.C., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL USA L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 |
|
AS | Assignment |
Owner name: SCALEIO LLC, MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC), MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL INTERNATIONAL L.L.C., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL USA L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 |