Abstract:
PROBLEM TO BE SOLVED: To implement an I/O task architecture in which a data access request (for example, stripe writing) is decomposed into a plurality of independently schedulable lower-level synchronous I/O tasks. SOLUTION: Resources needed by lower-level I/O tasks are dynamically assigned, as needed, for effective load and resource use balance to thereby achieve high scalability. A hierarchical order is assigned to the I/O tasks to ensure that there is a forward progression of their higher-level I/O task and to ensure that resources do not become deadlocked. COPYRIGHT: (C)2004,JPO
Abstract:
PROBLEM TO BE SOLVED: To provide a method and a system capable of maintaining data reliability, capable of deleting logically a failure disk, and capable of minimizing calculation and an access to a disk, for transferring or restoring the data or for executing recalculation of a parity. SOLUTION: A storage system transfers only a disk block including the allocated data, when the disk is failed (210), and treats an unallocated disk block logically zero when possible. When having no spare disk, a source data block is logically set to zero and the parity is recalculated for the RAID stripe related to the source data block (223). When having a spare, the unallocated block on the spare is logically or physically set to zero when transferred (222). A write operation into the failed disk is re-instructed to other non-failed disks, and a record in a using disk is transferred to the other non-failed disks to be maintained. COPYRIGHT: (C)2009,JPO&INPIT
Abstract:
PROBLEM TO BE SOLVED: To provide a method for controlling storage of data in a plurality of storage devices, for example, in a RAID array. SOLUTION: This method includes receiving a plurality of write requests associated with data and buffering the write requests. A file system defines a group of storage blocks, responsive to disk topology information. The group includes a plurality of storage blocks in each of the plurality of storage devices. Each data block of the data to be written is associated with a respective one of the storage blocks, for transmitting the association to the plurality of storage devices. COPYRIGHT: (C)2004,JPO
Abstract:
On disk failure, the storage system migrates only those disk blocks that included allocated data, and treats unallocated disk blocks as being logically zero when possible. When there is no spare disk, the source data block is logically set to zero and parity is recalculated for the RAID stripe associated with the source data block. When there is a spare, unallocated blocks on the spare are logically or physically set to zero upon migration. Write operations for the failed disk are redirected to other non-failing disks, and a record of which in-use disk blocks have been thus "migrated" to those other non-failing disks in maintained. Unused disk blocks are proactively set to zero. A target mirror copy is created using information regarding allocated disk blocks, by copying those blocks including allocated data or parity, and by clearing at the mirror those blocks not including any allocated data or parity.
Abstract:
On disk failure (210), the storage system migrates only those disk blocks that included allocated data, and treats unallocated disk blocks as being logically zero when possible. When there is no spare disk, the source disk block is logically set to zero and parity is recalculated for the RAID stripe associated with the source disk block (223). When there is a spare, unallocated blocks on the spare are logically or physically set to zero upon migration (222). Write operations for the failed disk are redirected to other non-failing disks, and a record of which in-use disk blocks have been thus 'migrated' to those other non-failing disks in maintained. Unused disk blocks are proactively set to zero. A target mirror copy is created using information regarding allocated disk blocks, by copying those blocks including allocated data or parity, and by clearing at the mirror those blocks not including any allocated.