Method and apparatus for virtual load regions in storage system controllers

• US 20070162708A1
• Filed: 01/06/2006
• Published: 07/12/2007
• Est. Priority Date: 01/06/2006
• Status: Active Grant

• Current Assignee: Dot Hill Systems Corporation (Seagate Technology Holdings Plc)
• Original Assignee: Dot Hill Systems Corporation (Seagate Technology Holdings Plc)
• Inventors: Wang, Yuanru
• Granted Patent: US 7,743,224 B2
• Time in Patent Office: Days
• US Class Current: 711/154
• CPC Class Codes: G06F 3/0607 by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device
• CPC Class Codes: G06F 3/0632 by initialisation or re-initialisation of storage systems
• CPC Class Codes: G06F 3/0689 Disk arrays, e.g. RAID, JBOD
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

Methods and apparatuses for facilitating the management of multiple controller code versions for implementing operational aspects of storage system controllers are provided. In particular, multiple versions of storage controller code are loaded into the physical memory of a storage controller. The logical region in which a particular controller code version is loaded may be designated in metadata as a primary, secondary or other region. The controller code that is associated with a logical version designated as the primary region is selected by the storage controller for execution upon a storage controller reboot. Accordingly, time consuming copy operations are not required in order to switch between different versions of storage controller code.

Claims

1. A method for managing storage controller code, comprising:

storing a first version of storage controller code in a first region of storage controller memory associated with a first storage controller;

storing a second version of storage controller code in a second region of said storage controller memory associated with said first storage controller;

maintaining region management information in storage controller memory including said first and second regions;

designating in said region management information said first region of storage controller memory as containing a primary version of storage controller code;

determining that said first region of storage controller memory contains said version of storage controller code designated as the primary version;

in response to said determining that said first region of storage controller memory contains said version of storage controller code designated as said primary version, executing said first version of storage controller code to control at least aspects of operation of said first storage controller, wherein at said time of executing said first version of storage controller code said second version of storage controller code is stored in said second region of said storage controller memory associated with said first storage controller.

2. The method of claim 1, wherein said first version of storage controller code is different than said second version of storage controller code, the method further comprising:

detecting a failure in operation of said first storage controller while executing said first version of said storage controller code;

in response to said detecting a failure of operation of said first storage controller while executing said first version of said storage controller code;

a) stopping execution of said first version of said storage controller code, and

starting execution of said second version of storage controller code; and

b) designating in said region management information said second region of storage controller memory as containing a primary version of storage controller code and removing a designation of said first region of storage controller memory as containing a primary version of storage controller code.

3. The method of claim 1, further comprising:

prior to said executing said first version of storage controller code;

reading from information associated with said first version of storage controller code a designation of said first version of said storage controller code as a primary version,

wherein said designating in said region management information said first region of storage controller memory as containing a primary version of said storage controller code is performed in response to said reading from information included in said first version of storage controller code a designation of said first version of storage controller code as a primary version.

4. The method of claim 3, further comprising:

reading from said information associated with said first version of storage controller code an instruction to reboot and start said first version of storage controller code as soon as said loading of said first version of storage controller code in said first region of storage controller memory is complete.

5. The method of claim 3, wherein said designating in said region management information said first region of storage controller memory as containing a primary version of said storage controller code comprises removing a designation in said region management information of said second region of storage controller memory as containing a primary version of said storage controller code.

6. The method of claim 4, further comprising:

prior to said loading a first version of storage controller code in said first region of storage controller memory, executing said second version of storage controller code to control at least aspects of operation of said first storage controller.

7. The method of claim 6, further comprising:

determining that said first version of storage controller code is less desirable than said second version of storage controller code;

in response to said determining that said first version of storage controller code is less desirable than said second version of storage controller code, designating in said region management information said second region of storage controller memory as containing a primary version of said storage controller code and removing a designation of said first region of storage controller memory as containing a primary version of said storage controller code.

8. The method of claim 4, wherein said loading said first version of storage controller code comprises downloading said first version of storage controller code to said storage controller from a location remote from said storage controller.

9. The method of claim 1, wherein said storage controller code comprises a number of storage controller code components, including at least one of a controller loader code component, a controller application code component, a controller field programmable gate array component, a complex programmable logic device code component, a power supply firmware code component, an embedded loop switch or fabric switch firmware code component, a management loader code component, and a management controller code component.

10. The method of claim 1, further comprising:

receiving a user command designating said second version of storage controller code as a primary version of storage controller code;

in response to said user command, designating in said region management information said second region of storage controller memory as containing a primary version of storage controller code and removing a designation in said region management information of said first region of storage controller memory as containing a primary version of storage controller code and executing said second version of storage controller code to control at least aspects of operation of said first storage controller, wherein said first version of storage controller code remains stored in said first region of storage controller memory.

11. A data storage system controller, comprising:

memory, including;

a first version of storage controller code loaded into a first region of said memory;

a second version of storage controller code loaded into a second region of said memory, wherein said first version of storage controller code is different than said second version of storage controller code;

region management information;

a processor, wherein said processor executes a one of said first and second versions of storage controller code from a corresponding one of said first and second regions in memory in response to a designation maintained in said region management information of said one of said first and second regions of said memory as containing a primary version of said storage controller code.

12. The controller of claim 11, wherein said memory comprises:

volatile memory, wherein said volatile memory includes said first and second regions of said memory; and

non-volatile memory, wherein said non-volatile memory includes said region management information.

13. The controller of claim 11, further comprising:

an interface, wherein at least said second version of said storage controller code is loaded into said second region of memory across said interface.

14. The controller of claim 11, wherein a user selection of one of said first and second versions of controller code as a primary version of said controller code determines said designation maintained in said region management information of said one of said first and second regions of said memory as containing a primary version of said storage controller code.

15. The controller of claim 11, wherein said first version of storage controller code is designated as said primary version of storage controller code and is executed from said first region of memory,

wherein said after executing said first version of storage controller code for a period of time said second version of storage controller code is loaded into said second region of memory,

wherein said second version of storage controller code is associated with information for changing said designation maintained in said region management information of said primary version of storage controller code from said first version to said second version;

wherein after said downloading said second version of storage controller code said storage controller is rebooted and said second version of storage controller code is executed from said second region of memory, and

wherein said first version of storage controller code remains loaded in said first region of memory but is not executed.

16. The controller of claim 11, wherein said controller stops execution of said second controller code from said second region of memory and resumes execution of said first controller code from said first region of memory in response to a user command reselecting said first controller code as a primary version of said controller code.

17. A data storage system, comprising:

means for controlling data input/output operations, including;

means for storing instructions for execution, including at least a first region containing a first set of execution instructions and a second region containing a second set of execution instructions, wherein said first set of execution instructions are different than said second set of execution instructions;

means for storing management information, wherein one of said first and second sets of execution instructions are designated as a primary set of execution instructions;

means for executing instructions, wherein one of said first and second sets of execution instructions designated as said primary set of execution instructions is executed from a corresponding one of said first and second regions.

18. The system of claim 17, further comprising:

means for administering;

wherein said means for controlling data input/output operations further comprises;

means for interfacing, wherein at least said second set of execution instructions is received from said means for administering.

19. The system of claim 17, wherein said means for storing management information comprises non-volatile memory means.

20. The system of claim 17, further comprising:

means for hosting data;

means for storing data in communication with said means for controlling data input/output operations, wherein data is written to and read from said means for storing data by said means for hosting data through said means for controlling data input/output operations.