US 8,549,236 B2Grant
Storage subsystem with multiple non-volatile memory arrays to protect against data losses
Issue Date:2013-10-01
•17 Claims
•4 Drawing Sheets
Abstract
A storage subsystem contains multiple non-volatile memory arrays that are accessible to a host system when the storage subsystem is connected thereto. The storage subsystem implements commands and/or modes for enabling the host system to create and use backup copies of files, such that the host system can recover when files become corrupted or otherwise lost. In one embodiment, the storage subsystem presents the non-volatile memory arrays to the host's operating system as distinct storage devices (e.g., ATA device 0 and 1), and implements special commands for copying data between these storage devices. The subsystem may alternatively present the memory arrays to the host operating system as a single storage device. The storage subsystem may have a standard form factor, such as a form factor commonly used for memory cards.
Metadata
Assignee
- SiliconSystems, Inc.
Inventors
- Mark S. Diggs
- David E. Merry, Jr.
Application Information
Application Number:US 11/611,705
Filing Date:2006-12-15
Priority Date:2006-12-15
Art Unit:2186
Classifications
IPC:
G06F12/00
Patent Drawings (4 sheets)
Description
BACKGROUND OF THE INVENTION
[0001] 1. Field of the Invention
[0002] The present invention relates to solid-state storage subsystems. More specifically, the present invention relates to providing data redundancy within a solid-state storage subsystem.
[0003] 2. Description of the Related Art
[0004] Companies are increasingly relying on portable solid-state storage subsystems to persistently store executable code and data. Typically, these subsystems are in the form of a memory card or drive that connects to an external port or connector of a host computer system. Because solid-state storage subsystems tend to be lighter, smaller and more shock resistant than magnetic disk drives, they are especially useful for applications involving portability. In many cases, the solid-state storage subsystem is used by the host system as a boot device (i.e., it stores the operating system code executed by the host computer), and/or is used to persistently store data generated or captured by the host computer.
[0005] One problem with existing solid-state storage subsystems is that they typically do not provide a sufficient degree of protection against data losses. Such data losses are typically caused by memory wear, memory array controller malfunctions, or rampant host software that overwrites important data. When such data losses occur, they can result in significant down time and lost revenue, especially if the storage subsystem is used to store operating system files or critical data.
SUMMARY
[0006] The present invention comprises a storage subsystem which contains multiple non-volatile memory arrays that are accessible to a host system when the storage subsystem is connected thereto. The storage subsystem implements commands and/or modes for enabling the host system to create and use backup copies of files, such that the host system can recover when files become corrupted or otherwise lost. In one embodiment, the storage subsystem presents the non-volatile memory arrays to the host's operating system as distinct storage devices (e.g., ATA device 0 and 1), and implements special commands for copying data between these disk drives. The subsystem may alternatively present the memory arrays to the host operating system as a single storage device. The storage subsystem may have a standard form factor, such as a form factor commonly used for memory cards.
BRIEF DESCRIPTION OF THE DRAWINGS
[0007] Specific embodiments of the invention will now be described with reference to the following drawings:
[0008] FIG. 1 is a block diagram illustrating a solid-state storage subsystem containing multiple non-volatile memory arrays and controllers according to one embodiment of the invention;
[0009] FIG. 2 illustrates an example command format for placing the storage subsystem into particular modes;
[0010] FIG. 3 illustrates an example command format for issuing “backup all” and “restore all” commands to the storage subsystem;
[0011] FIG. 4 illustrates an example command format for issuing mirror, backup and restore commands to the storage subsystem; and
[0012] FIG. 5 illustrates a solid-state storage subsystem according to another embodiment of the invention.
DETAILED DESCRIPTION OF SPECIFIC EMBODIMENTS
[0013] Specific embodiments of the invention will now be described with reference to the drawings. This description is intended to illustrate example implementations of, and applications for, the present invention, and is not intended to be limiting. Nothing in this description is intended to imply that any particular feature, characteristic, or mode of operation is a requirement of the invention. The invention is defined by the claims.
I. OVERVIEW
[0014] FIG. 1 illustrates a solid-state storage subsystem 112 with two non-volatile memory (NVM) arrays 116 and 117 according to one embodiment of the invention. The storage subsystem 112 is shown connected to a host system 110, which may, for example, be a portable computer, a router, a server, a medical device, or any other type of computing device. The host system 100 may, but need not, be designed to boot from, and execute application software stored on, the storage subsystem 112. The host system 100 may additionally or alternatively use the storage subsystem 112 to log data generated or captured by the host system. Typically, the storage subsystem is powered solely by the host system 110, although the storage subsystem may include a battery in some embodiments.
[0015] The host system 110 executes a special driver 113 or other software component that communicates with the subsystem 112 using the subsystem's command set. As discussed below, this command set preferably includes both standard ATA commands, and non-standard or “vendor-specific” commands for performing various types of data backup and restore operations. The subsystem 112 may also be used with hosts that do not execute special driver software (i.e., a standard operating system driver may be used), although the subsystem's non-standard backup and restore operations will not be available to the host in such configurations.
[0016] In the illustrated embodiment, the first NVM array 116 is controlled primarily by a first controller 114, and the second NVM array 117 is controlled primarily by a second controller 115. However, in other embodiments, both NVM arrays 116, 117 may be controlled exclusively by a single controller. Where two controllers 114 and 115 are provided as shown, each controller/memory array pair preferably appears to the host system 110 as a separate ATA disk drive, with one configured as device 0 (the “master”) and the other as device 1 (the “slave”). Thus, the host system 110 can selectively write data to, and read data from, each of the NVM arrays 116 and 117 using standard ATA disk drive commands. More specifically, each controller 114 and 115 is configured to write data to, and read data from, its respective the NVM array 116 and 117 in response to commands from the host system 110.
[0017] The design shown in FIG. 1 may alternatively be implemented such that one of the two devices (device 0 or device 1) or memory arrays is hidden from the host's operating system. With this approach, the “hidden” device or array can be accessed by the host via special vendor-specific commands, or, in some embodiments, by placing the storage subsystem in a “switch device” mode (discussed below) in which device 0 and 1 are effectively swapped. The ability to make one of the devices or arrays hidden may be a configuration option that can be set via a vendor-specific command. FIG. 5 , which is discussed below, illustrates one example of a subsystem architecture that is capable of using a hidden non-volatile memory array to maintain a backup copy of data written to an exposed non-volatile memory array.
[0018] Although two NVM arrays are used in the embodiment of FIG. 1 , a greater number of NVM memory arrays may be provided. For example, in embodiments based on the SCSI or standard (which allow more than two disk drives to share a common cable), three or more controller/memory-array pairs may be provided, each of which appears to the host as a respective SCSI or SATA disk drive. As another example, in an ATA implementation, three or more memory arrays may be provided with only two of these arrays being exposed to the host as ATA drives. The storage subsystem 112 may use the other memory array(s) to perform backup and restore operations transparently to the host, or to otherwise provide redundancy. For instance, the storage subsystem 112 could implement an internal RAID array (using, e.g., a RAID 0, 1, 2, 3, 4, or 5 configuration, as discussed below), but could present the array to the host as a single virtual disk drive.
[0019] Referring again to FIG. 1 , each controller 114, 115 accesses its respective NVM array 116, 117 via a corresponding address, data, and control busses. These busses are preferably cross-coupled such that the device 0 controller can directly access NVM array 1, and such that the device 1 controller can directly access NVM array 0. This arrangement enables each controller to execute various types of backup and restore operations, as described below, and also allows the data stored in both NVM arrays to be accessed in the event of a single-controller failure. During ordinary ATA operation, isolation circuitry (not shown) isolates device 0's address, data and control busses from those of device 1, such that the two controllers can access their respective NVM arrays in parallel. In other embodiments, rather than using cross coupled busses as shown, each controller 114, 115 may be capable of accessing the other's NVM array 116, 117 only indirectly via controller-to-controller communications.
[0020] As further illustrated in FIG. 1 , each NVM array 116, 117 is preferably subdivided into a “user” space and a “restricted” (non-user) space. The user space is the memory area that is exposed to the host's operating system (i.e., the host 110 can write data to, and read data from, this area) via standard ATA commands. In contrast, the restricted space can only be accessed by the host via one or more vendor-specific commands, and thus is not exposed to the host's operating system. The restricted spaces are used by the storage subsystem 112 to store various control parameters, including redundancy control parameters 140 used to implement backup and restore functions. The redundancy control parameters are preferably maintained in each NVM array in a predefined location within a 512-byte block that is read/write accessible via a particular vendor-specific command. The restricted spaces may also store firmware executed by the respective controllers 114, 115.
[0021] The storage subsystem 112 comprises a physical connector 150 for detachably connecting to the host 110. The connector 150 and associated signal interface preferably comply with an industry-standard such as a USB, SATA (Serial ATA), PC Card/PCMCIA, PCI Express, Firewire (IEEE 1394), Parallel ATA (PATA), CompactFlash (CF), Secure Digital (SD), or Memory Stick (among others). The subsystem 112 may alternatively be designed to communicate with the host 110 via a wireless interface, such as a Bluetooth interface, or via a non-standard interface.
[0022] Although not separately illustrated in FIG. 1 , the storage subsystem comprises a housing that houses the subsystem's electrical components. The housing and connector may, but need not, have a standard form factor such as a CF, PC Card/PCMCIA, MultiMediaCard, SmartMedia, Memory Stick, SecureDigital or hard disk drive (e.g., 2.5″ drive) form factor.
[0023] As will be apparent, the storage subsystem 112 provides data redundancy features that are typically available only in relatively large systems, such as disk array systems containing multiple magnetic disk drives. Unlike conventional disk array systems, however, the storage subsystem 112 can advantageously be implemented as a highly compact device that does not require any cabling, and that is powered by the host 110 via the same standard connection used for data. For example, the storage subsystem 112 can be implemented as a PCMCIA, CF or SD card or as a USB flash drive.
[0024] The two controllers 114 and 115 may be identical to each other. Each may be provided as separate integrated circuit, or both may be integrated within a common integrated circuit. As illustrated, each includes a respective buffer 152 (implemented in volatile RAM) for buffering data being written to or read from non-volatile memory, and includes interface circuitry 154 for implementing the appropriate signal interface for communicating with the host. The controllers 114 and 115 are preferably capable of executing firmware, although the functions embodied firmware may alternatively be implemented in state machine logic. In addition to implementing the ATA specification, the controllers 114, 115 may be capable of executing USB commands, PC Card commands, or CF commands, or commands associated with another specification.
[0025] The NVM arrays 116, 117 may be implemented using NAND memory devices, NOR memory devices, and/or any other type of solid-state non-volatile memory device. The solid-state memory devices may be physically divided into blocks, pages and sectors, as is known in the art.
II. SPECIAL MODES FOR CREATING AND USING BACKUP COPIES
[0026] To facilitate use of the dual NVM arrays to protect against losses, the storage subsystem 112 preferably implements two special modes, referred to as “mirror mode” and “switch device mode.” The subsystem 112 may be placed in one of these modes via a vendor-specific “mode set” command, the general format of which is shown in FIG. 2 . When such a mode set command is sent to the subsystem 112, each controller 114, 115 updates its respective mode register (not shown) to indicate the currently selected mode, and also updates the redundancy control parameters 140 stored in its respective NVM array. When the storage subsystem 112 is powered up, each controller 114, 115 loads some or all of the redundancy control parameters into its respective mode register to select the appropriate mode of operation.
[0027] As discussed in the following section, the storage subsystem also preferably implements a set of special (vendor-specific) commands for mirroring, backing up and restoring blocks of data. It should be understood that the particular modes and commands described herein are merely illustrative, and are not required to practice the invention. For example, in embodiments in which three of more separate NVM arrays are provided, a very different set of special modes and/or commands will typically be used.
Mirror Mode
[0028] When in mirror mode, the storage subsystem 112 writes to both NVM arrays 116, 117 when a standard write command is issued by the host. This mode may advantageously be used to efficiently mirror important files across the two NVM arrays/ATA devices. For example, a host system could initially place the subsystem in mirror mode, then write a set of OS (operating system) files, or other important files, to either device 0 or device 1 via standard ATA write commands. This would cause these files to be written to both devices/arrays, such that a backup copy is available if, for example, one copy becomes corrupted. As discussed below, mirrored copies of files can also be created using the mirror command.
[0029] The mirror mode is preferably implemented by having each controller 114, 115 perform a write to its respective NVM array whenever a standard write command is received, regardless of whether this command is directed to device 0 or device 1. Alternatively, the controller to which the write command is directed could write the data to both NVM arrays.
[0030] In some embodiments, the storage subsystem may also implement an “address constrained” mirror mode in which only those writes falling within a particular address range or zone are mirrored. For example, a particular zone may be created in one of the NVM arrays for storing mission critical data, and all writes to this zone may automatically be mirrored to a corresponding zone of the other NVM array. The storage subsystem 112 may create such zones in response to host command as disclosed in U.S. patent application Ser. No. 11/480,303, filed on Jun. 30, 2006, the disclosure of which is hereby incorporated by reference.
Switch Device Mode
[0031] When in “switch device” mode, the storage subsystem 112 switches the designations of device 0 and device 1 as recognized by the host system 110 for purposes of all read and write commands. Thus, if the host 110 issues a read or write command to device 0, the command will actually be handled by device 1 (and vice versa). This mode may be used to facilitate recovery after a failure or data loss. For example, if the host ordinarily boots from device 0 but is failing to do so (e.g., because the OS files on device 0 have become corrupted), and the OS files are also stored on device 1, the host/driver may place the subsystem 112 in the switch device mode prior to the next boot attempt. This advantageously causes the host to boot from device 1 without the need to modify the host's BIOS.
[0032] The switch device mode may also be used in other contexts. For instance, the host 110 may place the storage subsystem 112 in “switch device” mode (to cause the host to subsequently boot or otherwise execute from device 1) upon detecting that NVM array 0 is close to the end of its useful life. This determination may be made by reading out usage/wear-level statistics maintained by the storage subsystem, as disclosed in U.S. patent application Ser. No. 11/429,936, filed on May 8, 2006, the disclosure of which is hereby incorporated by reference. As another example, each controller 114, 115 may be capable of detecting, and reporting to the host, when an unusually high number of ECC or parity errors are occurring on reads from its respective NVM array; and the host may respond by placing the subsystem in “switch device” mode during a subsequent boot up.
Device Selector
[0033] In some embodiments, the storage subsystem 112 may include a device selector 121 (FIG. 1 ), such as a physical switch, that allows a user to manually place the subsystem into, and take the subsystem out of, the switch device mode. The device selector 121 may be provided in addition to, or in lieu of, a command that enables the host to do the same. If both are provided, the device selector may be given priority.
[0034] The device selector 121 advantageously allows the subsystem 112 to be placed in the “switch device” mode regardless of whether the subsystem is being used with a host capable of issuing vendor-specific commands. For instance, a user may experience a boot error while using the subsystem with a host system that does not have the subsystem's driver 113 or other special software installed thereon, and which is therefore incapable of sending a “switch device” command to the subsystem. In response to encountering the boot error, the user could use the device selector 121 to activate the “switch device” mode and then restart the host system 110.
III. DATA TRANSFER COMMANDS FOR BACKUP AND RESTORE OPERATIONS
[0035] In the embodiment shown in FIG. 1 , the storage subsystem 112 implements the following five vendor-specific commands for facilitating backup and restore operations: Backup All, Restore All, Mirror, Backup, Restore. Each of these commands is discussed below. An example of a command format that may be used for Backup All and Restore All commands is shown in FIG. 3 . A command format that may be used for Mirror, Backup and Restore commands is shown in FIG. 4 .
Backup All Command
[0036] The Backup All command directs the subsystem 112 to internally back up the entire contents of NVM array 0 (or a particular zone thereof, as discussed below) to NVM array 1. Any data that is stored in NVM array 1 (or the target zone thereof) is erased or overwritten during this process. This command may be used to efficiently set a recovery point in case of a failure. For example, a host system 110 that has been updating critical files in the storage subsystem 112 may issue a Backup All command to cause the device 0 controller 114 to copy some or all of the files in NVM array 0 to NVM array 1.
[0037] In some embodiments, the Backup All command may specify a particular zone to be backed up. In these scenarios, only the files stored in the specified zone of device 0 are copied to device 1. The zones may be created using vendor-specific commands as described in application Ser. No. 11/480,303, referenced above. For example, NVM array 0 can be divided into two zones, zone 1 and zone 2, with only zone 1 being used to store critical data. Rather than backing up all contents of NVM array 0, the backup operation can then be limited to zone 1.
Restore All Command
[0038] The Restore All command directs the storage subsystem 112 to internally copy the entire contents of NVM array 1 (or a designated zone thereof) to NVM array 0. Any data that is stored in NVM array 0 (or the target zone thereof) is erased or overwritten during this process. This command may be used to restore files on device 0 that have become corrupted. For example, if the host system 110 has crashed due to possible corruption of OS files on device 0, and has previously created a backup copy on device 1, the host may issue a Restore All command to the storage subsystem 112 and then attempt to re-boot from device 0.
Mirror Command
[0039] The Mirror command is the same as a standard write command, except that the storage subsystem 112 writes the data (via the respective controllers 114, 115) to both NVM arrays 116, 117. This command may be used in place of the mirror mode to create a backup copy of data being written to device 0, particularly when the quantity of data being backed up is small.
Backup Command
[0040] The backup command causes the subsystem 112 to internally read a designated set of sectors of device 0, and to write (back up) the read-out data to device 1. This command may be used in place of a Backup All command when the quantity of data being backed up is relatively small.
Restore Command
[0041] The Restore Command causes the subsystem to read a designated set of sectors in device 1, and to write the data read from these sectors to a corresponding set of sectors in device 0. This command may be used when, for example, the host detects that data stored in a particular sector or set of sectors of device 0 has likely become corrupted.
IV. STORAGE SUBSYSTEM WITH MASTER CONTROLLER
[0042] FIG. 5 illustrates a solid-state storage subsystem 512 according to another embodiment of the invention. In this embodiment, the storage subsystem includes N separate NVM arrays 514, each of which is controlled by a respective flash ATA disk controller 516. The number N of NVM arrays may, for example, be 2, 3, 4, 5, 8 or 12. As illustrated by the dashed lines in FIG. 5 , in some embodiments, each flash disk controller 516 may also be capable of accessing one or more of the other NVM arrays 514.
[0043] Each of the N flash disk controllers 516 communicates with a master controller 520. For example, as the master controller 520 receives read and write commands from the host 110 (which may be ATA commands, PC Card commands, USB commands, etc.), the master controller translates these commands into drive-specific ATA commands that are sent to the corresponding flash disk controllers 516. Data read by the flash disk controllers 514 is transferred to the master controller's buffer 525 before being transferred to the host 110. The master controller 520 includes interface circuitry 522 for communicating with the host 110 in accordance with one or more interface standards (as described above).
[0044] The master controller also includes a mode register 524 for enabling the host to specify a particular mode and configuration. The following are examples of modes that may be implemented.
-
- [0045] Single Virtualized Disk. When in this mode, the storage subsystem 512 presents itself to the host OS as a single, virtualized disk drive. This virtualized disk drive may include memory space of all or a particular subset of the N NVM arrays 514. If less than all of the NVM arrays are used to implement the virtualized disk drive, one or more of the NVM arrays may be hidden from the host OS and used for redundancy purposes (e.g., to store backup copies of files transparently to the host).
[0046] As with the embodiment of FIGS. 1-4 , the storage subsystem may include vendor-specific commands that enable the host to back up data to, and restore data from, the hidden NVM array or arrays.
-
- [0047] Device 0/Device 1. When in this mode, the storage subsystem 512 presents its storage resources to the host OS as two ATA disk drives, which may be configured as device 0 and device 1. The actual configuration depends on the value of N. For example, if N=2, one of the NVM arrays may correspond to device 0 and the other to device 1, and the subsystem may operate substantially as described for the preceding embodiment. As another example, if N=4, two of the NVM arrays may be used to implement device 0 and device 1 (respectively), and the other two may remain hidden from the host OS and be used for redundancy purposes-one for backing up device 0 data and the other for backing up device 1 data. Vendor-specific backup, restore and mirror commands may be supported to enable the host to backup data to, and restore data from, the hidden NVM arrays.
[0048] RAID array. When in this mode, the storage subsystem 512 effectively treats each NVM array 514 as a respective disk drive of a disk array, and operates the disk array in an appropriate RAID (Redundant Array of Inexpensive Disks) configuration. Depending on the value of N, one of the following RAID configurations (as well as others) may be used: RAID 0, 1, 2, 3, 4, 5, 6, 7, 0+1, or 10. The RAID array may be presented to the host 110 as a single virtualized disk drive.
[0049] The flash disk controllers 516 and the master controller 520 collectively form the main components of a flash disk array controller 530. The flash disk array controller 530 may be implemented as a single IC device or as multiple IC devices.
[0050] The storage subsystem 512 shown in FIG. 5 may otherwise be configured and may operate as described above for the embodiment of FIGS. 1-4 . The various features described in connection with the embodiments of FIGS. 1-4 may be incorporated into the embodiment of FIG. 5 , and vice versa.
IV. CONCLUSION
[0051] While certain embodiments have been described, these embodiments have been presented by way of example only, and are not intended to be limiting. Indeed, the novel methods and systems described herein may be embodied in a variety of other forms, including forms that do not provide all of the features and benefits described herein. Furthermore, various omissions, substitutions and changes in the form of the disclosed methods and systems may be made without departing from the invention. The invention is defined by the accompanying claims.
Claims
What is claimed is:
1. A storage subsystem comprising:
a first controller connected to, and being capable of writing data to and reading data from, a first solid-state non-volatile memory array;
a second controller connected to, and being capable of writing data to and reading data from, a second solid-state non-volatile memory array; and
a connector for connecting the storage subsystem to a host system, said connector coupled to the first and second controllers such that the first and second controllers are capable of receiving storage access commands from the host system;
wherein the first controller is capable of presenting at least a portion of the first non-volatile memory array to the host system as storage space of ATA device 0, and the second controller is capable of presenting at least a portion of the second non-volatile memory array to the host system as storage space of ATA device 1,
wherein both the first and second solid-state non-volatile memory arrays include operating system files associated with a boot up process of the host system;
wherein the storage subsystem is capable of being placed into a switch device mode in which data access commands issued by the host system to ATA device 1 are re-directed to the first non-volatile memory array, ATA device 0, and data access commands issued by the host system to ATA device 0 are re-directed to the second non-volatile memory array, ATA device 1, in response to an anticipated failure based on at least one of:
(1) a determination, based at least in part on usage or wear-level statistics of the first solid-state non-volatile memory array, that the first solid-state non-volatile memory array is close to the end of its useful life; and
(2) a command issued by the host system that is triggered at least in part by memory errors in the first solid-state non-volatile memory array reported by the first controller,
wherein the storage subsystem is configured to be placed in the switch device mode prior to an actual failure of the first solid-state non-volatile memory array,
wherein, due to the re-direction of data access commands, the storage subsystem provides the operating system files to the host system from the second solid-state non-volatile memory array when the host system attempts to read such files from the first solid-state non-volatile memory array to cause the host to boot up from the second solid-state non-volatile memory array without a prior failure of a data access command executed at the first non-volatile memory array and without a need to modify the host system's BIOS.
2. The storage subsystem of claim 1, in combination with said host system, wherein the host system is programmed to make the determination that the first solid-state non-volatile memory array is close to the end of its useful life.
3. The storage subsystem of claim 1, wherein the storage subsystem includes a physical switch that enables an operator to place the storage subsystem into the switch device mode.
4. The storage subsystem of claim 1, wherein the storage subsystem implements a command that enables the host system to place the storage subsystem into the switch device mode.
5. The storage subsystem as in claim 1, wherein the first and second controllers are capable of executing non-vendor-specific ATA storage access commands.
6. The storage subsystem of claim 5, wherein the first and second controllers are additionally capable of executing at least one vendor-specific command for backing up data from the first non-volatile memory array to the second non-volatile memory array.
7. The storage subsystem of claim 6, wherein the first and second controllers are additionally capable of executing at least one vendor-specific command for restoring backed up data from the second non-volatile memory array to the first non-volatile memory array.
8. The storage subsystem as in claim 1, wherein the storage subsystem is capable of being placed into a mirror mode in which, when the host system issues a command to write data to the first storage device, the storage subsystem automatically writes all of said data to both the first non-volatile memory array and the second non-volatile memory array.
9. The storage subsystem as in claim 1, wherein the first controller is additionally capable of accessing the second non-volatile memory array, and the second controller is additionally capable of accessing the first non-volatile memory array.
10. The storage subsystem as in claim 1, wherein the first and second controllers and the first and second memory arrays are housed within a housing that complies with a standard form factor used for memory cards.
11. The storage subsystem as in claim 10, wherein the standard form factor is one of the following: CompactFlash, SecureDigital, PCMCIA, MultiMediaCard, SmartMedia, Memory Stick.
12. The storage subsystem as in claim 1, wherein the connector is a USB connector.
13. The storage subsystem as in claim 1, further comprising a third controller that controls a third non-volatile memory array.
14. A storage subsystem, comprising:
first and second solid-state non-volatile memory arrays;
controller circuitry which is capable of writing data to, and reading data from, each of the first and second non-volatile memory arrays in response to commands received from a host system; and
a connector for connecting the storage subsystem to the host system, said connector coupled to the controller circuitry;
wherein the controller circuitry is capable of maintaining the second non-volatile memory array hidden from the host system while using the second non-volatile memory array to maintain a backup copy of data written by the host system to the first non-volatile memory array, such that the backup copy is maintained transparently to the host system, and
wherein the controller circuitry implements non-vendor-specific ATA storage access commands, and implements at least one vendor-specific command that enables the host system to access backup data stored in the second non-volatile memory array,
wherein the storage subsystem is capable of being placed into a switch device mode in which commands received from the host system for the first non-volatile memory array, presented to the host system as ATA device 0, are performed on the second non-volatile memory array, presented to the host system as ATA device 1, in response to an anticipated failure of the first non-volatile memory array based on at least one of:
(1) a determination, based at least in part on usage or wear-level statistics of the first non-volatile memory array, that the first non-volatile memory array is close to the end of its useful life; and
(2) a command issued by the host system that is triggered at least in part by memory errors in the first non-volatile memory array reported by the controller,
wherein the storage subsystem is configured to be placed in the switch device mode prior to an actual failure of the first solid-state non-volatile memory array,
wherein, due to the re-direction of data access commands, the storage subsystem provides the operating system files to the host system from the second solid-state non-volatile memory array when the host system attempts to read such files from the first solid-state non-volatile memory array to cause the host to boot up from the second solid-state non-volatile memory array without a prior failure of a data access command executed at the first non-volatile memory array and without a need to modify the host system's BIOS.
15. The storage subsystem as in claim 14, wherein the controller circuitry and the first and second non-volatile memory arrays are housed within a housing that complies with a standard form factor used for memory cards.
16. The storage subsystem of claim 14, in combination with said host system, wherein the host system is programmed to make the determination that the first non-volatile memory array is close to the end of its useful life.
17. The storage subsystem as in claim 14, wherein the controller circuitry is further capable of using the backup copy maintained in the second non-volatile memory array to restore lost data lost from the first non-volatile memory array.
Patent Citations (138)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4296464(A) | 1981-10-01 | Woods | Applicant |
| US4937736(A) | 1990-06-01 | Chang et al. | Applicant |
| US5018096(A) | 1991-05-01 | Aoyama | Applicant |
| US5442768(A) | 1995-08-01 | Sudoh | Applicant |
| US5721873(A) | 1998-02-01 | Tobita et al. | Applicant |
| US5737563(A) | 1998-04-01 | Shigeeda | Applicant |
| US5740397(A) | 1998-04-01 | Levy | Examiner |
| US5768612(A) | 1998-06-01 | Nelson | Applicant |
| US5784698(A) | 1998-07-01 | Brady et al. | Applicant |
| US5890219(A) | 1999-03-01 | Scaringella et al. | Applicant |
| US6000006(A) | 1999-12-01 | Bruce et al. | Applicant |
| US6014727(A) | 2000-01-01 | Creemer | Applicant |
| US6052799(A) | 2000-04-01 | Li et al. | Applicant |
| US6081878(A) | 2000-06-01 | Estakhri et al. | Applicant |
| US6088765(A) | 2000-07-01 | Ohtsuka | Applicant |
| US6092095(A) | 2000-07-01 | Maytal | Applicant |
| US6134631(A) | 2000-10-01 | Jennings, III | Applicant |
| US6173360(B1) | 2001-01-01 | Beardsley et al. | Applicant |
| US6223252(B1) | 2001-04-01 | Bandera et al. | Examiner |
| US6249838(B1) | 2001-06-01 | Kon | Applicant |
| US6269434(B1) | 2001-07-01 | Tanaka | Applicant |
| US6272589(B1) | 2001-08-01 | Aoki | Applicant |
| US6286087(B1) | 2001-09-01 | Ito et al. | Applicant |
| US6324627(B1) | 2001-11-01 | Kricheff et al. | Applicant |
| US6401214(B1) | 2002-06-01 | Li | Applicant |
| US6434648(B1) | 2002-08-01 | Assour et al. | Applicant |
| US6452950(B1) | 2002-09-01 | Ohlsson et al. | Applicant |
| US6484229(B1) | 2002-11-01 | Ichikawa et al. | Applicant |
| US6530034(B1) | 2003-03-01 | Okada et al. | Applicant |
| US6546456(B1) | 2003-04-01 | Smith et al. | Applicant |
| US6564173(B1) | 2003-05-01 | Arntz et al. | Applicant |
| US6633963(B1) | 2003-10-01 | Ellison et al. | Applicant |
| US6675281(B1) | 2004-01-01 | Oh et al. | Applicant |
| US6694381(B1) | 2004-02-01 | Lo et al. | Applicant |
| US6704012(B1) | 2004-03-01 | Lefave | Applicant |
| US6732221(B2) | 2004-05-01 | Ban | Applicant |
| US6735636(B1) | 2004-05-01 | Mokryn et al. | Examiner |
| US6754765(B1) | 2004-06-01 | Chang et al. | Applicant |
| US6761580(B2) | 2004-07-01 | Chang | Applicant |
| US6792519(B2) | 2004-09-01 | Constable et al. | Applicant |
| US6871272(B2) | 2005-03-01 | Butterworth | Applicant |
| US6892248(B2) | 2005-05-01 | Thayer | Applicant |
| US6944063(B2) | 2005-09-01 | Chen et al. | Applicant |
| US6944717(B2) | 2005-09-01 | Yoneyama et al. | Applicant |
| US6968434(B2) | 2005-11-01 | Kamano et al. | Applicant |
| US6976190(B1) | 2005-12-01 | Goldstone | Applicant |
| US6978398(B2) | 2005-12-01 | Harper et al. | Examiner |
| US6996623(B1) | 2006-02-01 | Kawano et al. | Applicant |
| US7024410(B2) | 2006-04-01 | Ito et al. | Applicant |
| US7054986(B2) | 2006-05-01 | Zhao et al. | Applicant |
| US7079395(B2) | 2006-07-01 | Garnett et al. | Applicant |
| US7103798(B2) | 2006-09-01 | Morita | Examiner |
| US7114051(B2) | 2006-09-01 | Guu et al. | Applicant |
| US7139871(B2) | 2006-11-01 | Mizuno | Applicant |
| US7139890(B2) | 2006-11-01 | Moran et al. | Applicant |
| US7210013(B2) | 2007-04-01 | Itoh et al. | Applicant |
| US7213117(B2) | 2007-05-01 | Wakabayashi et al. | Applicant |
| US7262961(B2) | 2007-08-01 | Motoe et al. | Applicant |
| US7277978(B2) | 2007-10-01 | Khatami et al. | Applicant |
| US7447807(B1) | 2008-11-01 | Merry et al. | Applicant |
| US7447944(B2) | 2008-11-01 | Hu | Applicant |
| US7464306(B1) | 2008-12-01 | Furuhjelm et al. | Applicant |
| US7467258(B2) | 2008-12-01 | Murayama | Examiner |
| US7509441(B1) | 2009-03-01 | Merry et al. | Applicant |
| US7596643(B2) | 2009-09-01 | Merry, Jr. et al. | Applicant |
| US7653778(B2) | 2010-01-01 | Merry et al. | Examiner |
| US7684417(B2) | 2010-03-01 | Imai et al. | Examiner |
| US7694188(B2) | 2010-04-01 | Raghuraman et al. | Applicant |
| US7765373(B1) | 2010-07-01 | Merry et al. | Applicant |
| US7912991(B1) | 2011-03-01 | Merry et al. | Applicant |
| US7962792(B2) | 2011-06-01 | Diggs et al. | Applicant |
| US8078918(B2) | 2011-12-01 | Diggs et al. | Examiner |
| US8122185(B2) | 2012-02-01 | Merry, Jr. et al. | Applicant |
| US8127048(B1) | 2012-02-01 | Merry et al. | Applicant |
| US8151020(B2) | 2012-04-01 | Merry, Jr. et al. | Applicant |
| US2002/0138602(A1) | 2002-09-01 | Vinberg | Applicant |
| US2003/0069671(A1) | 2003-04-01 | Yashiki et al. | Applicant |
| US2003/0131093(A1) | 2003-07-01 | Aschen et al. | Applicant |
| US2003/0188007(A1) | 2003-10-01 | Unger | Applicant |
| US2003/0200388(A1) | 2003-10-01 | Hetrick | Applicant |
| US2003/0227451(A1) | 2003-12-01 | Chang | Applicant |
| US2004/0128414(A1) | 2004-07-01 | Rudelic | Applicant |
| US2004/0145952(A1) | 2004-07-01 | Chen et al. | Applicant |
| US2004/0190877(A1) | 2004-09-01 | Matsuno et al. | Applicant |
| US2004/0210796(A1) | 2004-10-01 | Largman et al. | Examiner |
| US2004/0228197(A1) | 2004-11-01 | Mokhlesi et al. | Applicant |
| US2004/0246841(A1) | 2004-12-01 | Miyamoto | Applicant |
| US2004/0260967(A1) | 2004-12-01 | Guha et al. | Applicant |
| US2005/0036387(A1) | 2005-02-01 | Seal et al. | Applicant |
| US2005/0044454(A1) | 2005-02-01 | Moshayedi | Applicant |
| US2005/0047396(A1) | 2005-03-01 | Helm et al. | Applicant |
| US2005/0138306(A1) | 2005-06-01 | Panchbudhe et al. | Examiner |
| US2005/0160195(A1) | 2005-07-01 | Bruner et al. | Applicant |
| US2005/0196165(A1) | 2005-09-01 | Dybsetter et al. | Applicant |
| US2005/0197017(A1) | 2005-09-01 | Chou et al. | Applicant |
| US2005/0210098(A1) | 2005-09-01 | Nakamichi et al. | Examiner |
| US2005/0268007(A1) | 2005-12-01 | Nakabayashi | Applicant |
| US2005/0281112(A1) | 2005-12-01 | Ito et al. | Applicant |
| US2005/0289275(A1) | 2005-12-01 | Jung et al. | Examiner |
| US2006/0056813(A1) | 2006-03-01 | Sutardja | Applicant |
| US2006/0069866(A1) | 2006-03-01 | Miyazaki | Examiner |
| US2006/0085670(A1) | 2006-04-01 | Carver et al. | Applicant |
| US2006/0085836(A1) | 2006-04-01 | Lyons, Jr. et al. | Applicant |
| US2006/0095647(A1) | 2006-05-01 | Battaglia et al. | Applicant |
| US2006/0095699(A1) | 2006-05-01 | Kobayashi et al. | Applicant |
| US2006/0143426(A1) | 2006-06-01 | Wu | Applicant |
| US2006/0159098(A1) | 2006-07-01 | Munson et al. | Applicant |
| US2006/0179218(A1) | 2006-08-01 | Burkey | Examiner |
| US2006/0190696(A1) | 2006-08-01 | Ito et al. | Applicant |
| US2006/0200627(A1) | 2006-09-01 | Iftikar | Applicant |
| US2006/0212750(A1) | 2006-09-01 | Denninghoff et al. | Examiner |
| US2006/0248387(A1) | 2006-11-01 | Nicholson et al. | Applicant |
| US2006/0282709(A1) | 2006-12-01 | Shu et al. | Applicant |
| US2006/0294338(A1) | 2006-12-01 | Fisher et al. | Applicant |
| US2007/0008186(A1) | 2007-01-01 | Michaels et al. | Applicant |
| US2007/0053513(A1) | 2007-03-01 | Hoffberg | Applicant |
| US2007/0073944(A1) | 2007-03-01 | Gormley | Applicant |
| US2007/0079097(A1) | 2007-04-01 | Karnowski et al. | Applicant |
| US2007/0124130(A1) | 2007-05-01 | Brunet et al. | Applicant |
| US2007/0124542(A1) | 2007-05-01 | Ven | Applicant |
| US2007/0159710(A1) | 2007-07-01 | Lucas et al. | Applicant |
| US2007/0180328(A1) | 2007-08-01 | Cornwell et al. | Applicant |
| US2007/0201814(A1) | 2007-08-01 | Yamauchi | Applicant |
| US2007/0260811(A1) | 2007-11-01 | Merry et al. | Examiner |
| US2007/0266200(A1) | 2007-11-01 | Gorobets et al. | Applicant |
| US2007/0268791(A1) | 2007-11-01 | Grow et al. | Applicant |
| US2007/0283090(A1) | 2007-12-01 | Kaji et al. | Examiner |
| US2008/0046766(A1) | 2008-02-01 | Chieu et al. | Applicant |
| US2008/0109591(A1) | 2008-05-01 | Kim et al. | Applicant |
| US2008/0294669(A1) | 2008-11-01 | Narayanan | Examiner |
| US2009/0037643(A1) | 2009-02-01 | Ohtsuka et al. | Applicant |
| US2009/0063895(A1) | 2009-03-01 | Smith | Applicant |
| US2010/0011260(A1) | 2010-01-01 | Nagadomi et al. | Applicant |
| US2010/0023800(A1) | 2010-01-01 | Harari et al. | Examiner |
| US2012/0151130(A1) | 2012-06-01 | Merry, Jr. et al. | Applicant |
| EP589597(A3) | 1994-03-01 | Applicant | |
| JP5-100801 | 1993-04-01 | Applicant | |
| WO2006118646(A2) | 2006-09-01 | Applicant |
Non-Patent Literature (11)
- Andrew S. Tanenbaum, “Structured Computer Organization”, 1984, Prentice-Hall, Inc., 3rd edition, pp. 11-13.Examiner
- Webpage printed out from <http://www.m-systems.com/site/en-US/Support/DeveloperZone/Software/LifespanCalc.htm> on Jun. 13, 2006.Applicant
- Webpage printed out from <http://www.m-systems.com/site/en-US/Technologies/Technology/TrueFFS—Technology.htm> on Jun. 13, 2006.Applicant
- Webpage printed out from <http://www.techworld.com/storage/features/index.cfm?FeatureID=498> on Jun. 13, 2006.Applicant
- International Search Report and Written Opinion in PCT Application No. PCT/US2007/68490; Dated Sep. 29, 2008 in 11 pages.Applicant
- Document explaining prior sale.Applicant
- Silicondrive User'S Guide, SiSMART Function, Preliminary Version 2.2 Revision A, Feb. 2005.Applicant
- International Search Report and Written Opinion for International Application No. PCT/US09/32984, mailed on Mar. 17, 2009, in 10 pages.Applicant
- International Search Report and Written Opinion for International Application No. PCT/US09/33262, mailed on Mar. 25, 2009, in 10 pages.Applicant
- SFF Committee Specification, “Self-Monitoring, Analysis and Reporting Technology (SMART) SFF-8035i Revision 2.0”, Apr. 1, 1996 in 24 pages.Applicant
- European Search Report dated Dec. 22, 2011 received in European Application No. 07762018.5 in 10 pages.Applicant