Abstract: Methods, systems, and apparatus, including computer programs encoded on computer storage media, for maintaining fault tolerance for new writes in a storage system when one or more components of the storage system are unavailable. One of the methods includes determining that one or more first disks of a capacity object of a storage system are unavailable, wherein the storage system comprises a segment usage table identifying the plurality of segments of the capacity object; in response: identifying a plurality of available second disks, adding a plurality of new segments corresponding to the second disks to the capacity object, and adding data identifying the plurality of new segments to the segment usage table; and for each of one or more new write requests to the capacity object: identifying an available segment from the plurality of new segments, and writing data associated with the new write request to the identified available segment.

Abstract: A model generation apparatus (2000) acquires component failure data in which a usage status is associated with a failure record of a component. The model generation apparatus (2000) generates, for each of a plurality of component groups, a prediction model for predicting the number of failures of each component included in the component group by using the component failure data relating to the component belonging to the component group. The prediction model computes a prediction value of the total number of failures of the components belonging to a corresponding component group from the usage status, and computes a prediction value of the number of failures of each component belonging to the component group from the computed prediction value of the total number of failures.

Abstract: A storage system comprises a plurality of storage nodes each comprising one or more storage devices and a processor coupled to a memory. The storage system is configured to store data blocks across the storage devices of the storage nodes utilizing a redundant array of independent disks (RAID) arrangement. At least a given one of the storage nodes is configured to store a plurality of RAID metadata bitmaps in persistent storage of the storage node so as to be available for a recovery operation in the event of a detected failure, to identify a particular subset of the RAID metadata bitmaps to be updated in conjunction with an additional operation other than the recovery operation, and to temporarily store the identified subset of the RAID metadata bitmaps in the memory of the storage node in a manner determined based at least in part on an operation type of the additional operation.

Abstract: A data storage system includes a host configured to provide a read request; a plurality of storage devices constituting a redundant array of independent disks (RAID); and a RAID controller configured to a plurality of read commands in response to the read request, the read commands being provided to the plurality of storage devices according to a RAID setting, wherein one data storage device of the plurality of data storage devices includes a nonvolatile memory device; an error handling information storage circuit to store error handling information; and an error detection and correction circuit configured to detect an error in data output from the nonvolatile memory device according to a read command and to selectively correct the error according to the error handling information.

Abstract: A method, computer program product, and computer system for performing, by a computing device, a check on an internal secondary device on a first node during a boot software stack initialization. It may be determined that the internal secondary device is corrupt based upon, at least in part, the check. The first node may access a recovery operating system and an image repository of an internal secondary device on a second node. The internal secondary device on the first node may be rebuilt based upon, at least in part, the recovery operating system and the image repository of the internal secondary device on the second node.

Abstract: Systems and methods are provided for performing a test that relates to a service associated with an application programming interface. Based on a specification for the service, testing scenarios are generated, and then tests are executed. An output report that indicates a health of the service is then generated.

Abstract: Example implementations relate to method and management system for collecting contextual log files to an issue in a computing system. The method includes analyzing alert data to identify a current symptom associated with the issue in the computing system, and determining whether the current symptom exists in a first lookup table including a plurality of first symptoms and a plurality of first log categories. Each first symptom is mapped to one or more first log categories in the first lookup table. In response to determining that the current symptom exists in the first lookup table, the method includes collecting one or more log files from a plurality of log files corresponding to the one or more first log categories mapped to the current symptom, from the computing system. Further, the method includes transferring the one or more log files to an external computing system for performing diagnostics on the issue.

Abstract: A method and associated systems use DVFS performance-scaling technology to satisfy quality-of-service performance requirements when recovering a job that had been scheduled to run on a failed virtual machine. A Buffer Time specifies a duration of time remaining, at the time of failure, for the job to complete in order to satisfy the quality-of-service requirements. Depending on relative durations of time required to repair the failed virtual machine, to perform the job on an unscaled active-mode virtual machine, and to transfer the job to another virtual machine, the system determines whether to repair the failed virtual machine or to transfer the job. If the latter, the system then determines whether to select a destination virtual machine provisioned on a DVFS-compliant platform and, if so, the system scales the DVFS-compliant platform's performance to a level sufficient to complete the job within the Buffer Time.

Abstract: A method comprises retrieving operating conditions data comprising operational details of one or more components in at least one computing environment. Component replacement data and no fault found (NFF) data of the computing environment are also retrieved. The component replacement data comprises details about components that have been replaced in the computing environment. The NFF data comprises details about components incorrectly identified as having failed in the computing environment and symptoms leading to the incorrect identifications. The method also comprises generating a first mapping between given ones of the operational details and given ones of the replaced components, and generating a second mapping between given ones of the incorrectly identified components and given ones of the symptoms using one or more machine learning algorithms. Using the first and second mappings, at least one failed component is predicted based on one or more symptoms identified in a received support case.

Abstract: In response to detecting the failure of a data storage drive, a drive rebuild operation is performed. The drive rebuild operation is performed by periodically i) calculating a target rebuild rate that enables data previously stored on the failed data storage drive to be completely rebuilt on at least one other data storage drive within an expected drive rebuild time window, ii) calculating a new value for at least one drive rebuild parameter based on a value for the drive rebuild parameter corresponding to the target rebuild rate indicated by a static rebuild rate data structure and a current level of host I/O (Input/Output) activity, and iii) rebuilding the data previously stored on the failed data storage drive on the at least one other data storage drive for a predetermined time period with the at least one drive rebuild parameter set to the new value for the drive rebuild parameter.

Abstract: A system includes a memory device with multiple memory dies and at least a spare memory die. A processing device is coupled to the memory device. The processing device is to track a value of a write counter representing a number of write operations performed at the multiple memory dies. The processing device is to activate the spare memory die in response to detection of a failure of a first memory die of the multiple memory dies. The processing device is to store an offset value of the write counter in response to the detection of the activation of the spare memory die, the offset value representing the value of the write counter upon activation of the first spare memory die.

Abstract: A technique manages data within solid state device (SSD) storage. The technique involves, in response to writing data to a set of SSD storage components, consuming a set of recurring write quotas for the set of SSD storage components. Each recurring write quota identifies an amount of remaining usefulness for a respective SSD storage component, e.g., periodically allocated budgets for write operations based on measured (or counted) reliability and/or healthiness factors. The technique further involves, as the set of recurring write quotas are consumed, performing a set of quota evaluation operations to evaluate the set of recurring write quotas. The technique further involves, in response to a set of results from the set of quota evaluation operations, performing a set of remedial activities to control access to the data that was written to the set of SSD storage components.

Abstract: Systems and methods for analyzing a customer deployment in a converged or hyper-converged infrastructure are disclosed. A machine learning model is trained based upon historical usage data of other customer deployments. A k-means clustering is performed to generate a prediction as to whether a deployment is configured for optimal failover. Recommendations to improve failover performance can also be generated.

Abstract: Techniques are disclosed for re-executing a data processing pipeline following a failure of at least one of its components. The techniques may include a syntax for defining a compute graph associated with the data processing pipeline and receiving such a compute graph in association with a specific data processing pipeline. The technique may include executing the data processing pipeline, determining that a component of the data processing pipeline failed, and determining a portion of the data processing pipeline to execute/re-execute based at least in part on dependencies defined by the data processing pipeline in association with the failed component. Re-executing the one or more components may comprise retrieving an output saved in association with a component upon which the failed component depends.

Abstract: An apparatus comprises at least one processing device comprising a processor coupled to a memory; the at least one processing device being configured to: obtain a set of rebuild rate parameters for a given storage device from a storage array comprising a plurality of storage devices; and dynamically regulate a rebuild rate associated with a rebuild process for the given storage device based on the set of rebuild rate parameters obtained from the storage array for the given storage device. For example, the set of rebuild rate parameters include a rebuild capacity parameter and a rebuild time parameter.

Abstract: A data storage device including a non-volatile memory and a micro-controller is provided. The non-volatile memory includes a first block and a second block, wherein the first block stores firmware code. The micro-controller writes one predetermined string into the second block before an execution of the firmware code, and determines whether there is more than one predetermined string in the second block. In response to there being no more than one predetermined string in the second block, the micro-controller allows the execution of the firmware code and erases the predetermined string in the second block upon successful completion of a prerequisite procedure during the execution of the firmware code. In response to there being more than one predetermined string in the second block, the micro-controller does not allow the execution of the firmware code.

Abstract: A data storage erasure system may have a host connected to a plurality of data storage devices via a network controller with each of the plurality of data storage devices and the network controller connected to a pods controller and each of the plurality of the data storage devices having a device controller. A rebuild strategy can be generated with a rebuild module connected to the plurality of data storage devices, the network controller, and the pods controller. The rebuild strategy may be directed to minimize data rebuild times in the event of a failure in the plurality of data storage devices by executing the rebuild strategy in response to a detected or predicted failure in at least one data storage device of the plurality of data storage devices.

Abstract: Embodiments of dynamically increasing the resources for a partition to compensate for an input/output (I/O) recovery event are provided. An aspect includes allocating a first set of resources to a partition that is hosted on a data processing system. Another aspect includes operating the partition on the data processing system using the first set of resources. Another aspect includes, based on detection of an input/output (I/O) recovery event associated with operation of the partition, determining a compensation for the I/O recovery event. Another aspect includes allocating a second set of resources in addition to the first set of resources to the partition, the second set of resources corresponding to the compensation for the I/O recovery event. Another aspect includes operating the partition on the data processing system using the first set of resources and the second set of resources.

Abstract: Software tracing can be accomplished in a multitenant environment according to various examples of the present disclosure. In one example, a processing device can receive tracing information and a tenant identifier. The tracing information can indicate a sequence in which a group of microservices forming a software application executed in response to a request transmitted to the software application. The tenant identifier can correspond to a particular tenant among a group of tenants having access to an instance of the software application. The processing device can then select, based on the tenant identifier, a particular collector from among a group of collectors corresponding to the group of tenants. The processing device can forward the tracing information to the particular collector for causing the tracing information to be stored in a datastore corresponding to the particular tenant.

Abstract: Embodiments of information handling systems (HSs) and computer-implemented methods are provided herein to detect and recover from spurious PCIe device resets. One embodiment of a disclosed method is performed by a host processor of an IHS that includes a plurality of Peripheral Component Interconnect Express (PCIe) devices, each including a set of PCIe configuration registers containing configuration settings for the PCIe device. The disclosed method includes generating, in response to the IHS transitioning from a lower power state to a higher power state, a PCIe device table containing the configuration settings stored within the set of PCIe configuration registers for each of the PCIe devices; determining, in response to detecting a system management interrupt (SMI), whether or not a spurious reset has occurred for at least one of the PCIe devices; and recovering the at least one PCIe device if said determining indicates that a spurious reset has occurred for the at least one PCIe device.