Virtual ordered writes

• US 20050149666A1
• Filed: 03/01/2005
• Published: 07/07/2005
• Est. Priority Date: 03/25/2003
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Ofer, Adi, Meiri, David, Kopylovitz, Haim, Moreshet, Hana, Yoder, Benjamin W., Halstead, Mark J.
• Granted Patent: US 7,000,086 B2
• Time in Patent Office: Days
• US Class Current: 711/112
• CPC Class Codes: G06F 11/2064 while ensuring consistency
• CPC Class Codes: G06F 11/2074 Asynchronous techniques
• CPC Class Codes: G06F 12/0868 Data transfer between cache memory and other subsystems, e.g. storage devices or host systems
• CPC Class Codes: G06F 12/0871 Allocation or management of cache space
• CPC Class Codes: G06F 2003/0697 device management, e.g. handlers, drivers, I/O schedulers
• CPC Class Codes: G06F 2201/82 Solving problems relating to consistency ensuring consistency in mirrored systems G06F11/2064
• CPC Class Codes: G06F 2212/284 being distributed
• CPC Class Codes: G06F 3/0601 Interfaces specially adapted for storage systems
• CPC Class Codes: G06F 3/061 Improving I/O performance
• CPC Class Codes: G06F 3/0614 Improving the reliability of storage systems
• CPC Class Codes: G06F 3/0635 by changing the path, e.g. traffic rerouting, path reconfiguration
• CPC Class Codes: G06F 3/0656 Data buffering arrangements
• CPC Class Codes: G06F 3/0659 Command handling arrangements, e.g. command buffers, queues, command scheduling
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

Ordering data writes include a host computer providing a plurality of data writes to a primary storage device, the primary storage device assigning a first sequence number to data writes begun after a first time and before a second time, the primary storage device assigning a second sequence number, different from the first sequence number, to data writes begun after the second time, in response to completion of all writes assigned the first sequence number, the primary storage device transferring writes assigned the first sequence number to a secondary storage device, and, in response to the primary storage device transferring all writes assigned the first sequence number to the secondary storage device, the primary storage device sending a commit message to the secondary storage device. Ordering data writes may also include, in response to receiving a commit message from the primary storage device, the secondary storage device storing the data writes having the first sequence number.

Claims

1. A method of ordering data writes, comprising:

a primary storage device receiving a plurality of data writes;

the primary storage device associating data writes begun after a first time and before a second time with a first chunk of data;

the primary storage device associating data writes begun after the second time with a second chunk of data different from the first chunk of data;

after completion of all writes associated with the first chunk of data, the primary storage device initiating transfer of writes associated with the first chunk of data to a secondary storage device and

in response to receiving a message from the primary storage device separate from the first and second chunks of data, the secondary storage device storing the data writes associated with the first chunk of data.

3. A method, according to claim 1, further comprising:

after storing all of the data writes associated with the first chunk of data, the secondary storage device sending an acknowledge to the primary storage device;

following sending a message to the secondary storage device, the primary storage device suspending transferring data to the secondary storage device

following suspending transferring data, the primary storage device associating data writes with a third chunk of data, different from the first and second chunks of data, to subsequent data writes; and

in response to the secondary storage device sending an acknowledge to the primary storage device, the primary storage device resuming transferring data to the secondary storage device.

7. A method, according to claim 1, further comprising:

providing data writes to cache slots of the primary storage device.

8. A method, according to claim 7, further comprising:

in response to a data write being associated with the second chunk of data corresponding to a cache slot already associated with the first chunk of data, copying the data to a new cache slot.

9. A method, according to claim 7, further comprising:

the primary storage device using a first list of pointers to the cache slots for data writes associated with the first chunk of data;

the primary storage device using a second list of pointers to the cache slots for data writes associated with the second chunk of data; and

providing a cache stamp field in a header portion of each of the slots, the cache stamp field including a sequence number associated with the slot, wherein the sequence number corresponds to a particular one of the chunks of data and wherein the cache stamp field includes a password field that is written when the slot is first used and

in response to a slot no longer being used, the password field is cleared.

13. A method, according to claim 7, further comprising:

the primary storage device using a first cache only virtual device for the cache slots corresponding to data writes associated with the first chunk of data; and

the primary storage device using a second cache only virtual device for the cache slots corresponding to data writes associated with the second chunk of data.

33. A method, according to claim 1, wherein receiving a plurality of data writes includes receiving a plurality of data writes from a host.

2. (canceled)

4-6. -6. (canceled)

10-12. -12. (canceled)

14-17. -17. (canceled)

18. Computer executable code, embodied in a computer readable medium that orders data writes, comprising:

executable code that, when executed, associates data writes begun after a first time and before a second time with a first chunk of data;

executable code that, when executed, associates data writes begun after the second time with a second chunk of data different from the first chunk of data;

executable code that, when executed, initiates transfer of writes associated with the first chunk of data to a storage device after completion of all writes associated with the first chunk of data and

executable code that, when executed, causes the storage device to store the data writes associated with the first chunk of data in response to receiving a message separate from the first and second chunks of data.

20. Computer executable code, according to claim 18, further comprising:

executable code that, when executed, associating data writes with a third chunk of data, different from the first and second chunks of data, to subsequent data writes following suspending transferring data; and

executable code that, when executed, resumes transferring data to the storage device in response to the storage device acknowledging handling the message.

22. Computer executable code, according to claim 18, further comprising:

executable code that, when executed, provides data writes to cache slots;

executable code that, when executed, copies data to a new cache slot in response to a data write being associated with the second chunk of data corresponding to a cache slot already associated with the first chunk of data;

executable code that, when executed, uses a first list of pointers to the cache slots for data writes associated with the first chunk of data; and

executable code that, when executed, uses a second list of pointers to the cache slots for data writes associated with the second chunk of data.

25. Computer software executable code, according to claim 22, further comprising:

executable code that, when executed, provides a cache stamp field in a header portion of each of the slots, the cache stamp field including a sequence number associated with the slot, wherein the sequence number corresponds to a particular one of the chunks of data and wherein the cache stamp field also includes a password field that is written when the slot is first used; and

executable code that, when executed, clears the password field in response to a slot no longer being used.

28. Computer software, according to claim 22, further comprising:

executable code that, when executed, uses a first cache only virtual device for the cache slots corresponding to data writes associated with the first chunk of data; and

executable code that, when executed, uses a second cache only virtual device for the cache slots corresponding to data writes associated with the second chunk of data.

19. (canceled)

21. (canceled)

23-24. -24. (canceled)

26-27. -27. (canceled)

29-32. -32. (canceled)

34. A data storage device, comprising:

at least one disk drive that contains data;

at least one host adaptor, coupled to the at least one disk drive, that receives data to be stored on the at least one disk drive; and

at least one remote adaptor, coupled to the at least one disk drive and the at least one host adaptor, that transmits data to a remote storage device, wherein, in response to receipt of data by the at least one host adaptor, data writes begun after a first time and before a second time are associated with a first chunk of data, data writes begun after the second time are associated with a second chunk of data different from the first chunk of data and, after completion of all writes associated with the first chunk of data, a transfer of writes associated with the first chunk of data to the remote storage device is initiated, wherein, in response to receiving a message from the data storage device separate from the first and second chunks of data, the remote storage device stores the data writes associated with the first chunk of data.