|Publication number||US5933834 A|
|Application number||US 08/951,967|
|Publication date||Aug 3, 1999|
|Filing date||Oct 16, 1997|
|Priority date||Oct 16, 1997|
|Publication number||08951967, 951967, US 5933834 A, US 5933834A, US-A-5933834, US5933834 A, US5933834A|
|Original Assignee||International Business Machines Incorporated|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (22), Non-Patent Citations (9), Referenced by (141), Classifications (24), Legal Events (7)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This invention relates to a system for redistributing data onto an expanded array of disk drives, and more particularly to a video server system where video data is remapped onto an expanded array of disk drives.
A disk array is a collection of hard disk drives (HDDs) combined with array management software which controls the operation of the HDDS and presents them as one or more virtual HDDs to the host operating environment. The array management software masks the internal complexity of the disk array from the host operating environment by mapping virtual disk block addresses to member disk block addresses, so that the I/O operations are properly targeted to the physical storage. Arrays of HDDs are used to better match the I/O needs of a host computer with the performance limitations of disk drives. Using multiple storage devices to communicate data to the host system improves I/O performance for the host computer.
A Redundant Array of Independent Disks (RAID) system refers to a storage array where redundancy is provided. That is, part of the storage capacity is used to store redundant information about user's data stored on the remainder of the storage capacity. The redundant information enables regeneration of user data in the event that one of the arrays member disks or access path fails. Six levels of RAID systems are currently defined in the RAID book, "A Source for Disk Array Technology", Fourth Edition, The RAID Advisory Board.
RAID level 1 refers to data mirroring. In RAID level 2, a block of data is broken up and striped across a set of disk drives on a bit level and ECC codes for reconstructing each data block are stored on a separate set of disk drives. In order to access a block of data, all of the drives are accessed together. In RAID level 3, a block of data is also broken up and striped across a set of drives. Parity data for reconstructing each block is stored on a separate disk drive. In RAID level 4, a set of data blocks is striped across a set of drives, with parity data for the set of blocks (used for reconstructing one of the blocks of the set) stored on a separate disk drive. In a RAID level 4 system, each block can be accessed from a single drive. A RAID level 5 system is similar to a RAID level 4 system except that no one disk drive stores all of the parity. In a RAID level 6 system two blocks of parity are used for each set of data blocks such that two blocks of data can be reconstructed per set. RAID level 0, refers to a disk array where data is striped, but, redundancy is not used.
The host system executes application programs and device driver software which communicates with the storage devices. The application programs issue requests to access data stored on the storage devices which are routed through an I/O bus adaptor. The host system contains memory where data is read from and written to. An I/O bus adaptor provides an interface between the I/O bus and the host computer memory. The adaptor accepts commands from an I/O driver and relays the commands to the addressed storage devices. The I/O bus itself is the medium in which host commands, disk responses, and data are moved between bus adaptors and the storage devices. The storage devices provide block addressable random read/write access to data storage. An example of an I/O bus is the small computer storage interconnect (SCSI).
A disk controller connects a host computer's I/O bus to the storage device I/O bus using an I/O bus adaptor, such as a channel. The controller connects the host to additional storage devices and provides for greater I/O capacity. Each of the controller channels is an independent path for data which extend the subsystem's data transfer capacity.
An array stripe depth refers to the number of contiguously mapped virtual disk blocks in the array. The size of the stripe depth depends on the type of application requests that are made.
For application requests which specify large amount of data a significant portion of the I/O request execution time consists of the data transfer. If such requests are made to a virtual disk where the data is striped across each of the disks, most application I/O requests to the virtual disk will result in split I/O requests. For example, if there are four member disks in an array and requested data is mapped evenly across the three member data disks, each disk can independently be transferring its portion of the requested data. In that way, the I/O load is split among the disk drives.
Alternatively there can be request intensive application programs where a large number of small I/O requests are made. For such applications it is advantageous not to split the I/O request but to store all of the requested data on a single drive. For data transfer intensive application, such as image processing, the stripe depth should ideally be set so that the average I/O request is split across all members of the array on which the data is stored. For I/O request intensive applications, such as transaction processing, the stripe depth should be set so that the average I/O request has a small probability of being split across multiple array members.
An example of an I/O intensive application benefiting from striping data across a set of storage devices is a video server system. Computers are used to compress and store video material in digital format. This enables video on demand over telephone lines and pay-per-view movies in hotels. Compression technology enables the compression ratios which allow for the storage of videos on disk technology. Disk technology allow for random access of digital data and in an array subsystem provide high bandwidth. One such subsystem is described in commonly owned patent application Ser. No. 08/302,625, Belnapp et al., filed Sep. 8, 1994 hereby incorporated by reference.
The video server described in the application Ser. No. 08/302,065 provides a technique for serving many simultaneous streams from a single copy of data using data striping techniques like those used in RAID systems. Data striping involves the concept of a logical file whose data is partitioned to reside in multiple file components called stripes. Each stripe is stored on a different disk volume, thereby allowing the logical file to span multiple physical disks. The disk may be either local or remote. When the data is written to a logical file it is separated into logical lengths called segments that are placed sequentially into the stripes.
For example, a logical file for a video can be segmented into M segments or blocks, each of a specific size, e.g. 256 kilobytes. The last segment may only be partially filled with data. A segment of data is placed in the first stripe followed by the next segment that is placed in the second stripe, etc. When a segment has been written to each of the stripes the next segment is again written to the first stripe. Thus, if a file of M segments is being stripped into N stripes then stripe 1 will contain the segments 1, N+1, 2ŚN+1, etc., stripe 2 will contain the segments 2, N+2, 2ŚN+2, etc., until all M segments are stored in one of the N striped files.
In RAID systems the purpose of striping is to assure data integrity in case a disk is lost. A RAID system dedicates at least one of N disks to the storage of parity data that is used when data recovery is required. In the video server system the disk storage nodes are organized as RAID like structure, but parity data is not always required since a copy of the date video data can be available from a tape storage.
In a video server, striping is used for concurrency and bandwidth reasons. Each video presentation is separated into data blocks or segments that are spread across available disk drives to enable each video presentation to be accessed simultaneously from multiple disks without requiring multiple copies.
In a stream optimized video server using data striping for increased system capacity, both storage capacity and the number of streams is effected by adding additional disk drives. When disk drives are added, the data on existing drives needs to be restriped across the existing and newly added drives to enable the use of the additional capacity provided by the addition of the disk drives.
There is also a need to be able to simultaneously support objects striped over a variable number of disk drives. So that existing objects can be accessed while new objects are striped over a larger number of drives including the drives that the existing objects are using.
It is desirable that such a system continue to operate while data re-striping is taking place. This is true of systems other than video streamers using a storage array where additional storage capacity is being added.
It is an object of the invention to provide a system and method for re-striping objects stored in an array of storage devices without disrupting normal operations of the system and to run without requiring the host system. It is desirable that such a system re-stripe a large amount of objects in a production environment and re-stripe a small amount of objects in a test environment.
One or more of the foregoing problems are solved or objectives achieved using the present invention which provides a technique for re-striping data across a set of disk drives while the data is in use.
In a computer system having a processor, memory, and a set of storage units storing a set of objects, each object comprising a set of segments arranged in a set of original object stripes on separate storage units, a directory is maintained identifying an object name and a location of each stripe of the object in the set of storage units. A method is provided for re-striping the set of objects onto an expanded set of storage units comprising the set of storage units and at least one other additional storage unit. A list is maintained of each object to be copied onto the expanded set of storage units. Each segment is copied to a new set of stripes on a separate storage unit of the expanded set to create a new object while continuing to store an original copy of each segment of the list object in the original set of object stripes. The directory is updated to include a new object name and a new location of each new stripe of the new object. After all the list object segments are copied to the new stripes, the original copy of each list object segment is deleted and the new object is renamed in the directory to the list object name.
FIG. 1 is a block diagram of a system incorporating the current invention;
FIG. 2 illustrates a segmented logical file for a video and the striping of the segmented logical file on a plurality of disk drives according to the present invention;
FIG. 3 illustrates a directory for the segments of the video file;
FIG. 4 illustrates a mapping of the segments of a video file according to the present invention;
FIG. 5 illustrates a list of objects being copied; and
FIG. 6 is a flow chart of the process for re-striping objects according to the present invention.
FIG. 1 shows a video server system which provides for the presentation of multiple videos to multiple users. The video server 10 contains a low latency switch 12, which delivers data and control information between communication nodes 14, storage nodes 16 and control nodes 18.
The communication node 14 enables delivery of the data or the receiving of the data over an externally defined interface which are familiar to the broadcast industry such as NTFC, PAL, D1 and D2. The digital to video interface is embodied in a video card contained in a plurality of video ports 20 connected at the output of each communication node 14. The storage node 16 manages the storage medium such as disk arrays 22. The control node component 18 receives and executes control commands from an externally defined subsystem interface. An exemplary video server will contains 64 nodes with 31 communication nodes, 31 storage nodes, 2 control nodes interconnected with a low latency switch.
In a video presentation, one or more images may be logically related such as sequential frames of a film. The images may originally be generated by camera or digital computer or by a combination of a camera and video computer. A video presentation may also include an audio portion. The audio portion may be synchronized with the display of successive images. A data representation of a video presentation can be any suitable digital data format for representing one or more images and possibly audio. The digital data may be encoded or compressed.
A tape storage node 24 includes a tape library controller interface which enables access to multiple tape records contained in a tape library 26. A further interface enables access to other tape libraries via a SCSI bus interconnection.
The tape storage node 24 includes an internal system memory which enables buffering of video data. The system memory may be a portion of a PC which includes software for tape library and file management actions. A switch interface and buffer module enables interconnection between the tape storage and the switch. The buffer module partitions the data transfer into packets and adds a header portion to each package that is used by the switch to route the package.
Video data from the tape library is routed through the low latency switch to a disk storage node 22 to be made ready for substantially immediate access when needed. Each disk storage node includes a switch interface and a buffer module (not shown) which enables data to be transferred from or to a buffer video cache and storage interface module. The interface spreads received video data onto a plurality of disks. The disk storage node has an internal PC which includes software modules which provide storage node control, video file and disk control and RAID mapping for data stored on the disks.
Each disk storage node provides a more immediate level of video data availability than a tape storage node. Each disk storage node includes a cache for the video data so as to provide to even faster availability of video data.
The video streamer 10 has three external interfaces, a control interface which is an open system executing TCP/IP, a stream delivery interface using an industry standard such as NTSE, and an automation control interface which also uses industry standard control interfaces, such as Genloc or BlackBurst.
Application commands are issued to the video server over the control interface. When data load commands are issued, the control node breaks the incoming data file into segments and spreads it across one or more storage nodes. Material density and the number of simultaneous users of the data affect the placement of the data on the storage node. Increasing density and or simultaneous users implies the use of more storage nodes for capacity and bandwidth.
Data is moved between the disk storage nodes and the communication nodes via the low latency switch and a scheduling algorithm. The data stream that is emitted from the communication node interfaces multiplex to and from disk storage so that a single communication node stream uses a fraction of the capacity and bandwidth of each disk storage node.
The storage nodes are managed as a heterogenous group, each with a potentially different bandwidth capability and physical definition. The "create" command triggers the video server to allocate storage in one or more storage nodes for a multimedia file and its associated metadato. The create command specifies both the stream density and the maximum number of simultaneous users required.
In video applications there is a need to deliver multiple streams from the same data. This requirement translates to a need to read data at a high data rate. A logical video file has data partitioned to reside in multiple file components called stripes. Each stripe is allowed to exist on a different disk volume, thereby allowing the logical file to span multiple physical disks. The disk can be local or remote.
Referring to FIG. 2, when the data is written to the logical file 30 it is separated into logical lengths referred to as segments 32 that are placed sequentially into the stripes 34. A logical file for a video can be segmented into M segments or blocks, each of a specific size such as 256 kilobytes. The last segment may be only partially filled with data. A segment of data is placed on the first stripe followed by a next segment that is placed in the second stripe and so on. When a segment has been written to each of the stripes, the next segment is written to the first stripe. A file being striped into N stripes has stripe 1 containing segments 1, N+1, 2ŚN+1 and so on. Stripe 2 contains segments 2, N+2, 2ŚN+2 and so on. This is similar to the striping used in RAID systems except that parity data is not required because a copy of the video data is available from tape storage.
The separation of each video presentation into data blocks or segments that are spread across the available disk drives enable each video presentation to be accessed simultaneously from multiple drives without requiring multiple copies. The video presentation is striped according to play segments. A video file segmented into M segments and split into four stripes, stripe 1 contains segments 1, 5, 9, and so on of video file 1. Stripe 2 is a file containing segments 2, 6, 10, and so on of video file 1. Stripe 3 is a file containing segments 3, 7, 11, and so on of the video file. Stripe 4 is a file containing the segments 4, 8, 12, and so on of the video file until all M segments of the video file are contained in one of the four striped files.
There are a number of parameters that are used to customize the striping of each individual video. The segment size is selected so as to obtain a reasonably effective data rate from the disk without affecting latency and small enough to be able to be buffered in memory. A preferred segment size is 256 kilobytes and is constant for video presentation of data rates and ranges from 128 kilobytes per second to 512 kilobytes per second. If the video data rate is higher then it may be preferable to use a larger segment size. The segment size depends on the basic unit of I/O operation or the range of video presentation stored on the same media. Preferably a segment size contains half a second to two seconds of video data.
The number of stripes and the number of disks over which video data is distributed must be large enough to sustain the total data rate required and is computed individually for each video presentation based on the anticipated usage rate. More specifically each disk has a logical volume associated with it. Each video presentation is divided into component files, as many components as the number of stripes needed. Each component file is stored on a different logical volume.
The number of disks over which data for a video presentation is striped are managed as a set and can be thought of a very large physical disk. Striping allows a video file to exceed the size limit of the largest file that a system's physical file system will allow. The video data in general will not always require the same amount of storage in all disks in the set to balance the usage of the disk. When a video is striped the striping is begun from the disk that has the most free space.
Referring the FIG. 3, the striping algorithm uses a mapping structure directory 40 to map the segments of a video or data object to files stored on different DASD. The video directory contains the name, version, and segment size of each video object. The video directory also contains the number of stripes or files that the video is mapped onto, where each file is normally stored on a different HDD device, and the identity of the disk node storing each of the stripes in sequential order. As shown in FIGS. 2 and 3, the object V1 is initially striped over three DASD volumes D, E, and F. The directory in FIG. 3 provides the information for locating each of the segments. As shown in FIG. 2, when a new disk drive G is added, the video object is restriped over the expanded set of disk drives.
Referring to FIG. 4, when a new DASD volume, for example, G is added, the mapping structures for the existing objects are not changed and can be accessed while new data object V2 is striped over all of the volumes of the expanded array including the additional volume. Because each object has its own mapping structure the server can access objects striped over varying numbers of DASD volumes simultaneously. Additionally, the existing objects can be restriped (as shown in FIG. 2) by being copied to new locations on the expanded set of DASDs while the original version remains accessible, as long as the mapping structure for the original object remains in place. After the object is copied and restriped across all of the volumes of the expanded array, the original copy of the object can be deleted which allows the space to be reclaimed without disrupting operations.
The process for re-striping all of the objects onto the expanded set of DASDs will be described with reference to FIGS. 5 and 6. In order to restripe the objects, a list 50 is obtained of all objects on the video server. This list is maintained in the storage node memory. An empty list is created in the memory to store a list of all of the objects that become designated as not being restripable at the present time (all "non-restripable now" objects) 52. Another empty list is created in memory to store the list of objects that have been successfully re-striped.
The process for re-striping all of the objects onto the expanded array of DASDs involves going down the list of the objects currently stored in the original array of DASDs one object at a time. The first object on the list or next object in the list is selected. A determination is made if there is sufficient free space to make a copy of the selected object from the list 60. That is, whether there is sufficient space on each DASD for the copy of the stripe. If there is not sufficient space for each of the stripes of the selected object, the next object on the list, which may not be as large an object as the first selected object, is selected.
If none of the objects on the list can be selected because there is insufficient space to copy any of the objects, then the system waits for some time and then tries again to select the first object. The wait is to allow some of the objects currently stored in the array to be deleted to create more free space, since objects are regularly being deleted. The list of objects to be re-striped is also refreshed to reflect the current list of objects stored on the DASDs to be re-striped.
When there is enough free space in the array, a copy of the selected object on the list is made. A new temporary object with a new name is added to the object mapping directory (as shown in FIG. 3) and all the information of where the stripes are to be stored for the object segments are also stored in the object mapping directory for the newly created object (which is to be a copy of the selected object, re-striped over all of the DASDs of the expanded array) 62.
In order to copy the segments of the selected object, the selected object is opened for reading. The object is read into memory in small blocks, for example, 256 kilobytes blocks, starting from the beginning segment of the object 64. The read blocks are then written to the locations designated for the newly created temporary object.
When all the data for the selected object has been copied to the temporary object, the temporary object is renamed to the selected object name in the mapping structure directory 68. In order to rename the temporary object to the original selected object name, the original is deleted from the mapping structure 66. In a first embodiment, the renaming of the temporary object to the selected object name may require the original object to be deleted from the DASDs of the array. Otherwise, the original selected object can be deleted during a separate deletion process, depending on the system requirements.
After the object is copied, the selected object is deleted from the list of objects to be copied 70.
If any of the objects on the list of objects to be copied are deleted prior to its being fully copied and the temporary object being renamed, then the temporary object is also deleted 72.
This process continues until all objects have been restriped or deleted from the list of objects to be copied. The mapping structure allows objects to be accessed when striped over any number of the disk drives of the array less than or equal to the total number of disk drives in the system. Thus, when additional drives are added the existing objects can be accessed even though they are striped on fewer drives then the newly created temporary objects which will be striped over all the drives in the array including the newly added ones.
When none of the objects from the list of objects to be copied are selected because there is not sufficient free space, then all objects are moved to the "not restripable now" objects list 74. Also, if the object cannot be renamed because it is in use, the object name is moved to the list of nonrestripable now objects. A list of objects that have been restriped is also created as a reference.
The objects in the list of objects that cannot be restriped are again selected after the remaining objects on the list of objects to be re-striped have been selected and re-striped or moved to the list of objects that can not be re-striped at the current time 76. An attempt is again made to re-stripe the objects on the list of non-restripable now objects. Those that can are again placed in turn on another list. This process is repeated until all objects have been restriped or deleted.
The mapping structure provides the flexibility for simultaneously supporting objects striped over a variable number of disk drives which allows reading of existing objects while striping new objects over a larger number of drives including the drives that the existing objects are using.
The deletion of an original selected object when it is renamed after having been restriped allows the disk space to be reclaimed as soon as possible for re-striping of other objects, thus requiring a minimum amount of free space on the existing drives.
The ability to restripe objects based on a file containing a list of names allows re-striping to occur without disrupting normal operation and can be triggered to run unattended. This process is suitable for large amount of objects in a production environment. The base function ability to restripe objects by a specific name or name mask allows re-striping to occur still without disrupting normal operations and returning interactive messages. This process is also suitable for small amounts of objects focused on in a test environment.
Although described primarily in the context of a video server, it is well understood by those skilled in the art, that the re-striping of data in an array can be used by a number of applications.
The forgoing description is only illustrative of the invention. Alternatives and modifications can be devised by those skilled in the art without departing from the invention, The present invention is intended to include all such alternatives, modifications and variances which fall within the scope of the following claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4616319 *||Aug 6, 1984||Oct 7, 1986||General Electric Company||Storage of digitized video images on disk|
|US4638381 *||Aug 6, 1984||Jan 20, 1987||General Electric Company||Storage of digitized video images on disk|
|US4647986 *||Aug 6, 1984||Mar 3, 1987||General Electric Company||Storing video images on disk using video time base and retrieving the images using disk time base|
|US4674064 *||Aug 6, 1984||Jun 16, 1987||General Electric Company||Selectable bit length serial-to-parallel converter|
|US4680705 *||Sep 13, 1985||Jul 14, 1987||International Business Machines Corporation||Automatic data restructurer|
|US4953209 *||Oct 31, 1988||Aug 28, 1990||International Business Machines Corp.||Self-verifying receipt and acceptance system for electronically delivered data objects|
|US4989191 *||Jan 3, 1989||Jan 29, 1991||Frank Sheafen Kuo||Data processing system with mixed media memory packs|
|US5191410 *||Feb 5, 1991||Mar 2, 1993||Telaction Corporation||Interactive multimedia presentation and communications system|
|US5195092 *||Aug 30, 1991||Mar 16, 1993||Telaction Corporation||Interactive multimedia presentation & communication system|
|US5208665 *||Feb 15, 1991||May 4, 1993||Telaction Corporation||Presentation player for an interactive digital communication system|
|US5267351 *||Dec 22, 1989||Nov 30, 1993||Avid Technology, Inc.||Media storage and retrieval system|
|US5307456 *||Jan 28, 1992||Apr 26, 1994||Sony Electronics, Inc.||Integrated multi-media production and authoring system|
|US5438674 *||Jul 1, 1994||Aug 1, 1995||Data/Ware Development, Inc.||Optical disk system emulating magnetic tape units|
|US5502811 *||Sep 29, 1993||Mar 26, 1996||International Business Machines Corporation||System and method for striping data to magnetic tape units|
|US5502836 *||Jul 19, 1995||Mar 26, 1996||Ast Research, Inc.||Method for disk restriping during system operation|
|US5506977 *||Mar 14, 1994||Apr 9, 1996||Dell Usa, L.P.||Method and controller for minimizing reads during partial stripe write operations to a disk drive|
|US5537567 *||Mar 14, 1994||Jul 16, 1996||International Business Machines Corporation||Parity block configuration in an array of storage devices|
|US5586264 *||Sep 8, 1994||Dec 17, 1996||Ibm Corporation||Video optimized media streamer with cache management|
|US5603058 *||Sep 8, 1994||Feb 11, 1997||International Business Machines Corporation||Video optimized media streamer having communication nodes received digital data from storage node and transmitted said data to adapters for generating isochronous digital data streams|
|US5657468 *||Aug 17, 1995||Aug 12, 1997||Ambex Technologies, Inc.||Method and apparatus for improving performance in a reduntant array of independent disks|
|US5712976 *||Sep 8, 1994||Jan 27, 1998||International Business Machines Corporation||Video data streamer for simultaneously conveying same one or different ones of data blocks stored in storage node to each of plurality of communication nodes|
|JPH0667944A *||Title not available|
|1||IBM TDB, D. B. Johnson, et al., "Compressed/Encrypted Multimedia Objects Realtime Search and Retrieval", vol. 37, No. 03, Mar. 1994.|
|2||*||IBM TDB, D. B. Johnson, et al., Compressed/Encrypted Multimedia Objects Realtime Search and Retrieval , vol. 37, No. 03, Mar. 1994.|
|3||IBM TDB, J.W. Feeney, et al., "Bi-Directional Adapter for Multi-Media Network Applications", vol. 38, No. 10, Oct. 1996.|
|4||*||IBM TDB, J.W. Feeney, et al., Bi Directional Adapter for Multi Media Network Applications , vol. 38, No. 10, Oct. 1996.|
|5||IBM TDB, K. Dutke et al., "Multimedia Audio on Demand", vol. 37, No. 06B, Jun. 1994.|
|6||*||IBM TDB, K. Dutke et al., Multimedia Audio on Demand , vol. 37, No. 06B, Jun. 1994.|
|7||IBM TDB, R.F. Heisch, "Implementing Trace-Directed Program Restructuring for Global Data at the Postprocessing Level", vol. 37, No. 02B, Feb. 1994.|
|8||*||IBM TDB, R.F. Heisch, Implementing Trace Directed Program Restructuring for Global Data at the Postprocessing Level , vol. 37, No. 02B, Feb. 1994.|
|9||*||The RaidBook, A Source Book for Disk Array Technology, Fourth Edition, The Raid Advisory Board, Aug. 8, 1994.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US6304941 *||Apr 8, 1998||Oct 16, 2001||International Business Machines Corporation||Method and apparatus for reducing processor operations when adding a new drive to a raid-6 drive group|
|US6405219 *||Sep 24, 1999||Jun 11, 2002||F5 Networks, Inc.||Method and system for automatically updating the version of a set of files stored on content servers|
|US6427212||Nov 13, 1998||Jul 30, 2002||Tricord Systems, Inc.||Data fault tolerance software apparatus and method|
|US6449731||Aug 17, 1999||Sep 10, 2002||Tricord Systems, Inc.||Self-healing computer system storage|
|US6530036||Nov 15, 1999||Mar 4, 2003||Tricord Systems, Inc.||Self-healing computer system storage|
|US6725392||Oct 18, 2000||Apr 20, 2004||Adaptec, Inc.||Controller fault recovery system for a distributed file system|
|US6745284 *||Oct 2, 2000||Jun 1, 2004||Sun Microsystems, Inc.||Data storage subsystem including a storage disk array employing dynamic data striping|
|US6901206 *||Nov 27, 2002||May 31, 2005||Pelco||Digital video recorder file system|
|US7032090||Apr 8, 2003||Apr 18, 2006||International Business Machines Corporation||Method, system, and apparatus for releasing storage in a fast replication environment|
|US7069402||Jun 2, 2003||Jun 27, 2006||International Business Machines Corporation||Host-independent incremental backup method, apparatus, and system|
|US7113962||Jan 25, 2002||Sep 26, 2006||F5 Networks, Inc.||Method and system for automatically updating content stored on servers connected by a network|
|US7146524||Oct 25, 2002||Dec 5, 2006||Isilon Systems, Inc.||Systems and methods for providing a distributed file system incorporating a virtual hot spare|
|US7266555||Dec 8, 2000||Sep 4, 2007||Intel Corporation||Methods and apparatus for accessing remote storage through use of a local device|
|US7266556||Dec 29, 2000||Sep 4, 2007||Intel Corporation||Failover architecture for a distributed storage system|
|US7280738||Apr 9, 2001||Oct 9, 2007||International Business Machines Corporation||Method and system for specifying a selection of content segments stored in different formats|
|US7281168||Dec 29, 2000||Oct 9, 2007||Intel Corporation||Failover architecture for local devices that access remote storage|
|US7346720||Oct 21, 2005||Mar 18, 2008||Isilon Systems, Inc.||Systems and methods for managing concurrent access requests to a shared resource|
|US7386663 *||May 13, 2004||Jun 10, 2008||Cousins Robert E||Transaction-based storage system and method that uses variable sized objects to store data|
|US7386675||Oct 21, 2005||Jun 10, 2008||Isilon Systems, Inc.||Systems and methods for using excitement values to predict future access to resources|
|US7404036||Nov 23, 2005||Jul 22, 2008||International Business Machines Corporation||Rebalancing of striped disk data|
|US7428540||Oct 23, 2000||Sep 23, 2008||Intel Corporation||Network storage system|
|US7506034||Dec 29, 2000||Mar 17, 2009||Intel Corporation||Methods and apparatus for off loading content servers through direct file transfer from a storage center to an end-user|
|US7509448||Jan 5, 2007||Mar 24, 2009||Isilon Systems, Inc.||Systems and methods for managing semantic locks|
|US7509524||Aug 11, 2006||Mar 24, 2009||Isilon Systems Inc.||Systems and methods for a distributed file system with data recovery|
|US7509645||Feb 13, 2003||Mar 24, 2009||Intel Corporation||Methods and apparatus for load balancing storage nodes in a distributed network attached storage system|
|US7519629 *||Sep 30, 2004||Apr 14, 2009||International Business Machines Corporation||System and method for tolerating multiple storage device failures in a storage system with constrained parity in-degree|
|US7536470 *||Mar 12, 2005||May 19, 2009||Microsoft Corp.||Random access read/write media format for an on-demand distributed streaming system|
|US7551572||Oct 21, 2005||Jun 23, 2009||Isilon Systems, Inc.||Systems and methods for providing variable protection|
|US7590652||Aug 18, 2006||Sep 15, 2009||Isilon Systems, Inc.||Systems and methods of reverse lookup|
|US7590747||Jun 30, 2005||Sep 15, 2009||Intel Corporation||Distributed storage cluster architecture|
|US7593938||Dec 22, 2006||Sep 22, 2009||Isilon Systems, Inc.||Systems and methods of directory entry encodings|
|US7600075||Feb 28, 2008||Oct 6, 2009||Cousins Robert E||Transaction-based storage system and method that uses variable sized objects to store data|
|US7676691||Mar 9, 2010||Isilon Systems, Inc.||Systems and methods for providing nonlinear journaling|
|US7680836||Mar 16, 2010||Isilon Systems, Inc.||Systems and methods for a snapshot of data|
|US7680842||Aug 18, 2006||Mar 16, 2010||Isilon Systems, Inc.||Systems and methods for a snapshot of data|
|US7685126||Mar 23, 2010||Isilon Systems, Inc.||System and methods for providing a distributed file system utilizing metadata to track information about data stored throughout the system|
|US7707182||Nov 21, 2005||Apr 27, 2010||F5 Networks, Inc.||Method and system for automatically updating the version of a set of files stored on content servers|
|US7743033||Jul 19, 2007||Jun 22, 2010||Isilon Systems, Inc.||Systems and methods for providing a distributed file system utilizing metadata to track information about data stored throughout the system|
|US7752402||Aug 18, 2006||Jul 6, 2010||Isilon Systems, Inc.||Systems and methods for allowing incremental journaling|
|US7756898||Jul 13, 2010||Isilon Systems, Inc.||Systems and methods for notifying listeners of events|
|US7774325||Aug 10, 2010||Intel Corporation||Distributed network attached storage system|
|US7774466||Feb 13, 2003||Aug 10, 2010||Intel Corporation||Methods and apparatus for load balancing storage nodes in a distributed storage area network system|
|US7779048||Apr 13, 2007||Aug 17, 2010||Isilon Systems, Inc.||Systems and methods of providing possible value ranges|
|US7788303||Oct 21, 2005||Aug 31, 2010||Isilon Systems, Inc.||Systems and methods for distributed system scanning|
|US7797283||Sep 14, 2010||Isilon Systems, Inc.||Systems and methods for maintaining distributed data|
|US7818501||Jun 11, 2008||Oct 19, 2010||International Business Machines Corporation||Rebalancing of striped disk data|
|US7822932||Oct 26, 2010||Isilon Systems, Inc.||Systems and methods for providing nonlinear journaling|
|US7844617||Jun 4, 2010||Nov 30, 2010||Isilon Systems, Inc.||Systems and methods of directory entry encodings|
|US7848261||Dec 7, 2010||Isilon Systems, Inc.||Systems and methods for providing a quiescing protocol|
|US7870345||Jan 11, 2011||Isilon Systems, Inc.||Systems and methods for managing stalled storage devices|
|US7877545||Sep 8, 2008||Jan 25, 2011||Cisco Technology, Inc.||Online restriping technique for distributed network based virtualization|
|US7882068||Aug 21, 2007||Feb 1, 2011||Isilon Systems, Inc.||Systems and methods for adaptive copy on write|
|US7882071||Feb 1, 2011||Isilon Systems, Inc.||Systems and methods for a snapshot of data|
|US7886111||Feb 8, 2011||Compellent Technologies||System and method for raid management, reallocation, and restriping|
|US7899800||Mar 1, 2011||Isilon Systems, Inc.||Systems and methods for providing nonlinear journaling|
|US7900015||Mar 1, 2011||Isilon Systems, Inc.||Systems and methods of quota accounting|
|US7917474||Oct 21, 2005||Mar 29, 2011||Isilon Systems, Inc.||Systems and methods for accessing and updating distributed data|
|US7937421 *||May 3, 2011||Emc Corporation||Systems and methods for restriping files in a distributed file system|
|US7937528||May 3, 2011||Cousins Robert E||Transaction-based storage system and method that uses variable sized objects to store data|
|US7949636||May 24, 2011||Emc Corporation||Systems and methods for a read only mode for a portion of a storage system|
|US7949692||May 24, 2011||Emc Corporation||Systems and methods for portals into snapshot data|
|US7953704||Aug 18, 2006||May 31, 2011||Emc Corporation||Systems and methods for a snapshot of data|
|US7953709||May 31, 2011||Emc Corporation||Systems and methods for a read only mode for a portion of a storage system|
|US7962779||Jun 9, 2008||Jun 14, 2011||Emc Corporation||Systems and methods for a distributed file system with data recovery|
|US7966289||Jun 21, 2011||Emc Corporation||Systems and methods for reading objects in a file system|
|US7971021||Jun 28, 2011||Emc Corporation||Systems and methods for managing stalled storage devices|
|US7975025||Jul 5, 2011||F5 Networks, Inc.||Smart prefetching of data over a network|
|US7984324||Jul 19, 2011||Emc Corporation||Systems and methods for managing stalled storage devices|
|US8005865||May 27, 2010||Aug 23, 2011||Emc Corporation||Systems and methods for notifying listeners of events|
|US8010493||Mar 4, 2010||Aug 30, 2011||Emc Corporation||Systems and methods for a snapshot of data|
|US8015156||Sep 6, 2011||Emc Corporation||Systems and methods for a snapshot of data|
|US8015216||Sep 6, 2011||Emc Corporation||Systems and methods of providing possible value ranges|
|US8027984||Sep 4, 2009||Sep 27, 2011||Emc Corporation||Systems and methods of reverse lookup|
|US8051425||Oct 28, 2005||Nov 1, 2011||Emc Corporation||Distributed system with asynchronous execution systems and methods|
|US8054765||Nov 8, 2011||Emc Corporation||Systems and methods for providing variable protection|
|US8055711||Nov 8, 2011||Emc Corporation||Non-blocking commit protocol systems and methods|
|US8060521||Nov 15, 2011||Emc Corporation||Systems and methods of directory entry encodings|
|US8082379||Mar 23, 2009||Dec 20, 2011||Emc Corporation||Systems and methods for managing semantic locks|
|US8112395||Feb 7, 2012||Emc Corporation||Systems and methods for providing a distributed file system utilizing metadata to track information about data stored throughout the system|
|US8131926||Oct 20, 2004||Mar 6, 2012||Seagate Technology, Llc||Generic storage container for allocating multiple data formats|
|US8140623||Jun 8, 2006||Mar 20, 2012||Emc Corporation||Non-blocking commit protocol systems and methods|
|US8176013||May 8, 2012||Emc Corporation||Systems and methods for accessing and updating distributed data|
|US8181065||Mar 2, 2010||May 15, 2012||Emc Corporation||Systems and methods for providing nonlinear journaling|
|US8195905||Jun 5, 2012||Emc Corporation||Systems and methods of quota accounting|
|US8200632||Jan 14, 2011||Jun 12, 2012||Emc Corporation||Systems and methods for adaptive copy on write|
|US8214334||Jul 3, 2012||Emc Corporation||Systems and methods for distributed system scanning|
|US8214400||Jul 3, 2012||Emc Corporation||Systems and methods for maintaining distributed data|
|US8230193||Feb 7, 2011||Jul 24, 2012||Compellent Technologies||System and method for raid management, reallocation, and restriping|
|US8238350||Oct 28, 2005||Aug 7, 2012||Emc Corporation||Message batching with checkpoints systems and methods|
|US8255373 *||Aug 28, 2012||Microsoft Corporation||Atomic multiple modification of data in a distributed storage system|
|US8286029||Oct 9, 2012||Emc Corporation||Systems and methods for managing unavailable storage devices|
|US8326923||May 17, 2011||Dec 4, 2012||F5 Networks, Inc.||Smart prefetching of data over a network|
|US8335807 *||Dec 18, 2012||Sprint Communications Company, L.P.||File distribution system and method|
|US8356013||Jan 15, 2013||Emc Corporation||Systems and methods for a snapshot of data|
|US8356150||Sep 30, 2010||Jan 15, 2013||Emc Corporation||Systems and methods for providing nonlinear journaling|
|US8380689||Feb 19, 2013||Emc Corporation||Systems and methods for providing nonlinear journaling|
|US8539056||Aug 2, 2006||Sep 17, 2013||Emc Corporation||Systems and methods for configuring multiple network interfaces|
|US8549223 *||Oct 29, 2009||Oct 1, 2013||Symantec Corporation||Systems and methods for reclaiming storage space on striped volumes|
|US8555108||May 10, 2011||Oct 8, 2013||Compellent Technologies||Virtual disk drive system and method|
|US8560880||Jun 29, 2011||Oct 15, 2013||Compellent Technologies||Virtual disk drive system and method|
|US8625464||Nov 1, 2010||Jan 7, 2014||Emc Corporation||Systems and methods for providing a quiescing protocol|
|US8630528||Jul 13, 2007||Jan 14, 2014||International Business Machines Corporation||Method and system for specifying a selection of content segments stored in different formats|
|US8677065||Apr 3, 2011||Mar 18, 2014||Robert E. Cousins||Transaction-based storage system and method that uses variable sized objects to store data|
|US8966080||Apr 13, 2007||Feb 24, 2015||Emc Corporation||Systems and methods of managing resource utilization on a threaded computer system|
|US9021295||Oct 7, 2013||Apr 28, 2015||Compellent Technologies||Virtual disk drive system and method|
|US9047216||Oct 14, 2013||Jun 2, 2015||Compellent Technologies||Virtual disk drive system and method|
|US9164855 *||Jan 27, 2014||Oct 20, 2015||Primos Storage Technology, LLC||Transaction-based storage system and method that uses variable sized objects to store data|
|US9244625||Jul 23, 2012||Jan 26, 2016||Compellent Technologies||System and method for raid management, reallocation, and restriping|
|US20010047400 *||Dec 29, 2000||Nov 29, 2001||Coates Joshua L.||Methods and apparatus for off loading content servers through direct file transfer from a storage center to an end-user|
|US20020069324 *||Dec 6, 2000||Jun 6, 2002||Gerasimov Dennis V.||Scalable storage architecture|
|US20020146236 *||Apr 9, 2001||Oct 10, 2002||International Business Machines Corporation||Method and system for specifying a selection of content segments stored in different formats|
|US20030103055 *||Nov 27, 2002||Jun 5, 2003||Pelco||Digital video recorder file system|
|US20030135514 *||Oct 25, 2002||Jul 17, 2003||Patel Sujal M.||Systems and methods for providing a distributed file system incorporating a virtual hot spare|
|US20040078465 *||Feb 13, 2003||Apr 22, 2004||Coates Joshua L.||Methods and apparatus for load balancing storage nodes in a distributed stroage area network system|
|US20040078466 *||Feb 13, 2003||Apr 22, 2004||Coates Joshua L.||Methods and apparatus for load balancing storage nodes in a distributed network attached storage system|
|US20040088297 *||Feb 13, 2003||May 6, 2004||Coates Joshua L.||Distributed network attached storage system|
|US20040153479 *||Nov 14, 2003||Aug 5, 2004||Mikesell Paul A.||Systems and methods for restriping files in a distributed file system|
|US20040205311 *||Apr 8, 2003||Oct 14, 2004||International Business Machines Corporation||Method, system, and apparatus for releasing storage in a fast replication environment|
|US20040243775 *||Jun 2, 2003||Dec 2, 2004||Coulter Robert Clyde||Host-independent incremental backup method, apparatus, and system|
|US20050246393 *||Jun 30, 2005||Nov 3, 2005||Intel Corporation||Distributed storage cluster architecture|
|US20060050697 *||Mar 12, 2005||Mar 9, 2006||Microsoft Corporation||Random access read/write media format for an on-demand distributed streaming system|
|US20060074995 *||Sep 30, 2004||Apr 6, 2006||International Business Machines Corporation||System and method for tolerating multiple storage device failures in a storage system with constrained parity in-degree|
|US20060129775 *||Feb 10, 2006||Jun 15, 2006||Hulsey John A||Method, system and apparatus for releasing storage in a fast replication environment|
|US20070030291 *||Feb 24, 2004||Feb 8, 2007||Drazen Lenger||Gaming machine transitions|
|US20070091790 *||Oct 21, 2005||Apr 26, 2007||Passey Aaron J||Systems and methods for providing variable protection|
|US20070094269 *||Oct 21, 2005||Apr 26, 2007||Mikesell Paul A||Systems and methods for distributed system scanning|
|US20070094431 *||Oct 21, 2005||Apr 26, 2007||Fachan Neal T||Systems and methods for managing concurrent access requests to a shared resource|
|US20070094452 *||Oct 21, 2005||Apr 26, 2007||Fachan Neal T||Systems and methods for using excitement values to predict future access to resources|
|US20070118689 *||Nov 23, 2005||May 24, 2007||Hyde Joseph S Ii||Rebalancing of striped disk data|
|US20070171919 *||Oct 28, 2005||Jul 26, 2007||Godman Peter J||Message batching with checkpoints systems and methods|
|US20080021907 *||Jul 19, 2007||Jan 24, 2008||Patel Sujal M||Systems and methods for providing a distributed file system utilizing metadata to track information about data stored throughout the system|
|US20080046476 *||Aug 18, 2006||Feb 21, 2008||Anderson Robert J||Systems and methods for a snapshot of data|
|US20080235449 *||Jun 11, 2008||Sep 25, 2008||International Business Machines Corporation||Rebalancing of striped disk data|
|US20080263089 *||Feb 28, 2008||Oct 23, 2008||Cousins Robert E||Transaction-Based Storage System and Method That Uses Variable Sized Objects to Store Data|
|US20100106934 *||Oct 24, 2008||Apr 29, 2010||Microsoft Corporation||Partition management in a partitioned, scalable, and available structured storage|
|US20100205231 *||Oct 6, 2009||Aug 12, 2010||Cousins Robert E||Transaction-based storage system and method that uses variable sized objects to store data|
|CN1692356B||Nov 14, 2003||Jun 4, 2014||易斯龙系统公司||Systems and methods for restriping files in a distributed file system|
|EP1182868A2 *||Jul 9, 2001||Feb 27, 2002||Quantel Limited||Improvements in file servers|
|EP1894103A2 *||Jun 5, 2006||Mar 5, 2008||Cisco Technology, Inc.||Online restriping technique for distributed network based virtualization|
|EP1894103A4 *||Jun 5, 2006||May 5, 2010||Cisco Tech Inc||Online restriping technique for distributed network based virtualization|
|WO2004046971A1 *||Nov 14, 2003||Jun 3, 2004||Isilon Systems, Inc.||Systems and methods for restriping files in a distributed file system|
|U.S. Classification||714/6.21, 711/114, 711/170, 714/6.12, 707/999.103, 348/E05.008|
|International Classification||H04N21/23, H04N21/21, G06F3/06|
|Cooperative Classification||Y10S707/99944, G06F3/0613, G06F3/0638, H04N21/21, G06F3/0655, H04N21/23, G06F3/0689, G06F11/1096|
|European Classification||H04N21/23, H04N21/21, G06F3/06A4T, G06F3/06A6L4R, G06F3/06A4F, G06F3/06A2P4, G06F11/10R5|
|Oct 16, 1997||AS||Assignment|
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AICHELEN, TYKY;REEL/FRAME:008780/0858
Effective date: 19971016
|Dec 11, 2002||FPAY||Fee payment|
Year of fee payment: 4
|Nov 20, 2006||FPAY||Fee payment|
Year of fee payment: 8
|Mar 7, 2011||REMI||Maintenance fee reminder mailed|
|Jun 10, 2011||SULP||Surcharge for late payment|
Year of fee payment: 11
|Jun 10, 2011||FPAY||Fee payment|
Year of fee payment: 12
|Jul 12, 2011||AS||Assignment|
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTERNATIONAL BUSINESS MACHINES CORPORATION;REEL/FRAME:026664/0866
Owner name: GOOGLE INC., CALIFORNIA
Effective date: 20110503