Abstract: A queue-based non-volatile memory (NVM) hardware assist card, information handling system, and method are disclosed herein.

Abstract: A queue-based non-volatile memory (NVM) hardware assist card, information handling system, and method are disclosed herein.

Abstract: A disclosed storage management method includes detecting an unrecoverable failure associated with a logical block of a first physical storage device that is one of a plurality of storage devices within a redundant virtual drive that also includes a hot spare drive. Data for the unrecoverable block may be rebuilt from data in the remaining storage devices and stored in a logical block of the hot spare drive. One or more logical block maps may be maintained to identify unrecoverable logical blocks and to indicate the logical blocks and storage devices to which each of the unrecoverable logical blocks is relocated. I/O operations that access “good” logical blocks are normally while accesses to unrecoverable logical blocks are rerouted according to the logical block map. One or more unrecoverable thresholds may be supported to initiate operations to replace storage devices containing unrecoverable blocks exceeding an applicable threshold.

Abstract: A chassis determines a steady state power consumption of each node in the chassis based upon real-time monitoring of power consumption of the nodes. The chassis also determines a power allocation for each node based upon the steady state power consumptions for the nodes. The chassis also determines a total power allocation for the chassis based upon the steady state power consumptions for the nodes. The chassis also determines a source and amount of input power for the chassis based upon the total power allocation for the chassis. The steady state power consumption of a node may be determined by sampling the power consumption of the node during a window period, and setting the steady state consumption of the node to a range if the values of the samples during the window period are within the assigned range.

Abstract: A storage management method includes receiving a degrade signal indicating a degraded state of a virtual disk associated with a host system. Rebuild-flush operations may be performed. The operations may include writing, to the virtual disk and also to a hot spare drive (HSP) associated with the virtual disk, valid-modified data, stored in a host storage cache, associated with the virtual disk. In contrast, valid-unmodified storage cache data associated with the virtual disk, may be written to the HSP only. After the rebuild-flush completes, the virtual disk may be rebuilt. During rebuild, however, any cached-LBA may be skipped where traditional RAID rebuild operations are performed for un-cached LBAs only.

Abstract: An information handling system recognizes PCIe-based RAID volumes, including RAID virtual disks spanning two or more NVMe storage drives, while performing boot, hibernation, and crash-dump functions, rather than treating each storage device and its corresponding storage controller separately. The information handling system may perform a two-tiered discovery/initialization process during which a storage protocol function driver detects and initializes physical storage controllers, a storage controller bus driver virtualizes all physical storage controllers of a particular storage protocol and exposes a single virtualized storage controller for the protocol. A virtual miniport driver may then detect RAID volumes associated with the virtual storage controller and initialize the detected RAID stack(s).

Abstract: A storage management method includes receiving a degrade signal indicating a degraded state of a virtual disk associated with a host system. Rebuild-flush operations may be performed. The operations may include writing, to the virtual disk and also to a hot spare drive (HSP) associated with the virtual disk, valid-modified data, stored in a host storage cache, associated with the virtual disk. In contrast, valid-unmodified storage cache data associated with the virtual disk, may be written to the HSP only. After the rebuild-flush completes, the virtual disk may be rebuilt. During rebuild, however, any cached-LBA may be skipped where traditional RAID rebuild operations are performed for un-cached LBAs only.

Abstract: A disclosed storage management method includes detecting an unrecoverable failure associated with a logical block of a first physical storage device that is one of a plurality of storage devices within a redundant virtual drive that also includes a hot spare drive. Data for the unrecoverable block may be rebuilt from data in the remaining storage devices and stored in a logical block of the hot spare drive. One or more logical block maps may be maintained to identify unrecoverable logical blocks and to indicate the logical blocks and storage devices to which each of the unrecoverable logical blocks is relocated. I/O operations that access “good” logical blocks are normally while accesses to unrecoverable logical blocks are rerouted according to the logical block map. One or more unrecoverable thresholds may be supported to initiate operations to replace storage devices containing unrecoverable blocks exceeding an applicable threshold.

Abstract: An information handling system recognizes PCIe-based RAID volumes, including RAID virtual disks spanning two or more NVMe storage drives, while performing boot, hibernation, and crash-dump functions, rather than treating each storage device and its corresponding storage controller separately. The information handling system may perform a two-tiered discovery/initialization process during which a storage protocol function driver detects and initializes physical storage controllers, a storage controller bus driver virtualizes all physical storage controllers of a particular storage protocol and exposes a single virtualized storage controller for the protocol. A virtual miniport driver may then detect RAID volumes associated with the virtual storage controller and initialize the detected RAID stack(s).

Abstract: A chassis determines a steady state power consumption of each node in the chassis based upon real-time monitoring of power consumption of the nodes. The chassis also determines a power allocation for each node based upon the steady state power consumptions for the nodes. The chassis also determines a total power allocation for the chassis based upon the steady state power consumptions for the nodes. The chassis also determines a source and amount of input power for the chassis based upon the total power allocation for the chassis. The steady state power consumption of a node may be determined by sampling the power consumption of the node during a window period, and setting the steady state consumption of the node to a range if the values of the samples during the window period are within the assigned range.