System and method for journal recovery for multinode environments
First Claim
1. A method of journal recovery in a multi-node environment comprising:
- determining whether a block was last updated by a first node;
determining whether the block is associated with a lock held by a second node;
writing the block to a final location if the block was last updated by the first node and is not associated with a lock held by the second node; and
not writing the block to the final location if the block was last updated by the first node but is associated with a lock held by the second node.
7 Assignments
0 Petitions
Accused Products
Abstract
A system and method are disclosed for providing journal recovery in a multi-node environment which comprises determining whether a block was last updated by a first node; determining whether the block is associated with a lock held by a second node; and writing the block to a final location if the block is not associated with a lock held by the second node. In another embodiment, a system and method are disclosed for providing journal recovery in a multi-node environment which comprises determining whether a block is associated with metadata; determining whether the block is associated with a lock held by a surviving node; and writing the block to a final location if the block is not associated with a lock held by the surviving node.
-
Citations
17 Claims
-
1. A method of journal recovery in a multi-node environment comprising:
-
determining whether a block was last updated by a first node; determining whether the block is associated with a lock held by a second node; writing the block to a final location if the block was last updated by the first node and is not associated with a lock held by the second node; and not writing the block to the final location if the block was last updated by the first node but is associated with a lock held by the second node. - View Dependent Claims (2, 3, 4)
-
-
5. A system of journal recovery in a multi-node environment comprising:
-
a processor configured to determine whether a block was last updated by a first node;
determine whether the block is associated with a lock held by a second node;
write the block to a final location if the block was last updated by the first node and is not associated with a lock held by the second node; and
not write the block to the final location if the block was last updated by the first node but is associated with a lock held by the second node; anda memory coupled to the processor, wherein the memory provides the processor with instructions.
-
-
6. A system of journal recovery in a multi-node environment comprising:
-
a first node, wherein the first node has failed; a second node; a third node configured to determine whether a block was last updated by the first node;
determine whether the block is associated with a lock held by the second node;
write the block to a final location if the block was last updated by the first node and is not associated with a lock held by the second node; and
not write the block to the final location if the block was last updated by the first node but is associated with a lock held by the second node. - View Dependent Claims (7, 8, 9)
-
-
10. A method of journal recovery in a multi-node environment comprising:
-
determining whether a block is associated with metadata; determining whether the block is associated with a lock held by a surviving node; writing the block to a final location if the block was associated with the metadata and is not associated with a lock held by the surviving node; and not writing the block to the final location if the block was associated with the metadata but is associated with a lock held by the second node. - View Dependent Claims (11)
-
-
12. A system of journal recovery in a multi-node environment comprising:
-
a first node, wherein the first node has failed; a second node; a third node configured to determine whether a block is associated with metadata;
determine whether the block is associated with a lock held by the second node;
write the block to a final location if the block was associated with the metadata and is not associated with a lock held by the second node; and
not write the block to the final location if the block was associated with the metadata but is associated with a lock held by the second node. - View Dependent Claims (13, 14, 15)
-
-
16. A computer program product for journal recovery in a multi-node environment, the computer program product being embodied in a computer readable storage medium and comprising computer instructions for:
-
determining whether a block was last updated by a first node; determining whether the block is associated with a lock held by a second node; writing the block to a final location if the block was last updated by the first node and is not associated with a lock held by the second node; and not writing the block to the final location if the block was last updated by the first node but is associated with a lock held by the second node.
-
-
17. A computer program product for journal recovery in a multi-node environment, the computer program product being embodied in a computer readable storage medium and comprising computer instructions for:
-
determining whether a block is associated with metadata; determining whether the block is associated with a lock held by a surviving node; writing the block to a final location if the block was associated with the metadata and is not associated with a lock held by the surviving node; and not writing the block to the final location if the block was associated with the metadata but is associated with a lock held by the surviving node.
-
Specification