Systems and methods for providing nonlinear journaling

• US 7,676,691 B2
• Filed: 08/18/2006
• Issued: 03/09/2010
• Est. Priority Date: 08/18/2006
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: Isilon Systems Incorporated (Dell Technologies Inc.)
• Inventors: Husted, Justin M., Passey, Aaron J., Godman, Peter J., Fachan, Neal T.
• Primary Examiner(s): LE, DIEU MINH T
• Application Number:
  US11/507,073
• Publication Number:
  US 20080126365A1
• Time in Patent Office: 1,299 Days
• Field of Search: 714/15, 714/5, 714/6, 714 7- 11, 711/112, 711/114, 711/154
• US Class Current: 714/15
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 11/1474 in transactions G06F16/20 takes precedence

Abstract

In one embodiment, systems and methods are provided for nonlinear journaling. In one embodiment, groups of data designated for storage in a data storage unit are journaled into persistent storage. In one embodiment, the journal data is recorded nonlinearly. In one embodiment, a linked data structure records data and data descriptors in persistent storage.

Claims

1. A method of journaling data for a data storage unit with multiple storage devices, wherein the data storage unit may continue to accept requests to write data while one of the storage devices is unavailable for storage, comprising:

journaling data to be written on a plurality of storage devices of a data storage unit, wherein data that is journaled corresponds to a plurality of transactions, and the data to be written for each of the plurality of transactions is to be distributed among two or more of the plurality of storage devices;

determining when one of said storage devices is unavailable; and

keeping the data journaled for said one storage device while said storage device is unavailable for storage, while data journaled for an available storage device may be removed from a journal once the data has been written to the available storage device; and

replaying journal data for said one unavailable storage device after said one unavailable storage device becomes available for storage.

2. The method of claim 1, wherein said replaying does is not done for any of said plurality of storage devices other than said one unavailable storage device.

3. The method of claim 1, wherein said replaying is conditioned on whether said data corresponds to a transaction with a transaction state specified for replay.

4. The method of claim 3, wherein the data storage unit is part of a system comprising a plurality of storage units that execute transactions global to the system, and wherein said transaction state specified for replay is a state indicating that the system has committed to execute said transaction.

5. The method of claim 1, wherein the journaled data to be written on a plurality of storage devices is written redundantly for a subset of said plurality of storage devices.

6. A system supporting per-drive journal replay for a data storage unit with multiple storage devices, wherein the data storage unit may continue to accept requests to write data while one or more of the storage devices are unavailable for storage, comprising:

a plurality of storage devices;

persistent memory; and

a program module configured to journal data to be written on the plurality of storage devices, wherein data that is journaled corresponds to a plurality of transactions, and the data to be written for each of the plurality of transactions is to be distributed among two or more of the plurality of storage devices;

said program module further configured to keep in said persistent memory journal data corresponding to a subset of said plurality of storage devices that are temporarily unavailable to store said journaled data;

wherein data journaled for an available storage device may be removed from a journal once the data has been written to the available storage device;

said program module further configured to replay journal data for an unavailable storage device after said unavailable storage device becomes available for storage.

7. The system of claim 6, wherein said plurality of storage devices are an array of hard-disk drives.

8. The system of claim 6, wherein said persistent memory resides on the data storage unit, and said program module is executed on the storage unit.

9. The system of claim 6, wherein said replaying is not done for any of said plurality of storage devices other than said unavailable storage device.

10. The system of claim 6, wherein said replaying is conditioned on whether said data corresponds to a transaction with a transaction state specified for replay.

11. The system of claim 10, wherein the data storage unit is part of a distributed system comprising a plurality of storage units that execute transactions global to the distributed system, and wherein said transaction state specified for replay is a state indicating that the distributed system has committed to execute said transaction.

12. A method of journaling data for a data storage unit with multiple storage devices, wherein said data storage unit is part of a system comprising a plurality of data storage units that execute transactions global to the system, wherein the data storage unit may continue to accept requests to write data while one of the storage devices is unavailable for storage, comprising:

journaling data to be written on a plurality of storage devices of the data storage unit, wherein data that is journaled corresponds to transactions that are distributed among two or more of the plurality of storage devices;

determining when one of said storage devices is unavailable;

keeping the data journaled for said one storage device while said storage device is unavailable for storage; and

replaying journal data for said one storage device after said one storage device becomes available for storage, wherein journal data corresponding to a given transaction is only replayed if said transaction includes a data write to said one storage device.

13. The method of claim 12, wherein said replaying is not done for any of said plurality of storage devices other than said one storage device.

14. The method of claim 12, wherein said replaying is conditioned on whether said data corresponds to a transaction with a transaction state specified for replay.

15. The method of claim 14, wherein said transaction is global to the system, and said transaction state specified for replay is a state indicating that the system has committed to execute said transaction.