Abstract: A file system is implemented in a system comprising an anonymous-write storage device. A request for a file system operation that comprises semantics of the file system to receiving the request is received. The file system translates the file system operation to one or more commands that effect the file system operation while maintaining consistency with operation of the anonymous-write storage device. The one or more commands comprise one or more of updating file system metadata, sending a request to the anonymous-write storage device, or receiving a response from the anonymous-write storage device. The anonymous-write storage device is configured to write data in an append-only format and determine locations of data write operations agnostic of input of a write location from the file system. Metadata is updated to indicate results of the file system operation.

Abstract: A reduced throughput maintenance mode for adaptively managing input/output (I/O) operations within a resilient group of storage nodes. A first storage node in a resilient group of storage nodes is classified as operating in a normal throughput mode, and a second storage node in the resilient group is classified as operating in a reduced throughput mode. While the second node is classified as operating in the reduced throughput mode, read and write I/O operations are queued for the resilient group. The read I/O operation is prioritized for assignment to the first node, so as to reduce I/O load on the second node while it operates in the reduced throughput mode. The write I/O operation is queued to the second node, so as to maintain synchronization of the second node with the resilient group while it operates in the reduced throughput mode.

Abstract: An interface receives storage requests for storing data in a software-defined storage network using an append-only storage scheme. The requests include an identifier of a data object to be stored. The requests are agnostic of hardware-specific details of the storage devices. A virtualization layer accesses space allocation data for the storage devices; and policies for prioritizing performance. Based on the data and policies, a physical storage location at the plurality of storage devices is selected for storing the data object. Metadata is generated for the data object indicating that the data object is an append-only object and mapping the physical storage location of the data object to the identifier. The request is translated to instructions for storing the data object at the physical storage location using the append-only storage scheme. The data object is stored at the physical storage location using the append-only storage scheme.

Abstract: An interface is instantiated for receiving storage requests for storing data in a software-defined storage network using an append-only storage scheme. The interface receives requests that are agnostic of interfaces and hardware-specific details of the storage devices of the software-defined storage network. A request comprises an identifier of a data object to be stored in the software-defined storage network using the append-only storage scheme. Metadata is generated for the data object indicating that the data object is an append-only object; and the request is translated to instructions for storing the data object in the storage devices using the append-only storage scheme. The data object is stored at one of the plurality of storage devices based on the instructions. The metadata is updated to indicate a mapping between the data object and a stored location of the data object.

Abstract: The techniques described herein are configured to improve the remanufacturing process by waiting to rebuild selective data items stored on a storage device that is unavailable. A storage device is unavailable when it is taken offline and/or disconnected from a network. The storage device may be taken offline due to a failed component (e.g., an actuator arm, an actuator head, damage to the underlying storage media, etc.). The storage device comprises multiple independent logical units, where a logical unit is a uniquely addressable portion of a storage device that is visible and/or that is exposed to a host. Accordingly, the techniques described herein are configured to conserve resources by selectively rebuilding data items stored in logical units of an offline storage device that are not affected by a remanufacturing process implemented due to a failed component.

Abstract: A file system is implemented in a system comprising an anonymous-write storage device. A request for a file system operation that comprises semantics of the file system to receiving the request is received. The file system translates the file system operation to one or more commands that effect the file system operation while maintaining consistency with operation of the anonymous-write storage device. The one or more commands comprise one or more of updating file system metadata, sending a request to the anonymous-write storage device, or receiving a response from the anonymous-write storage device. The anonymous-write storage device is configured to write data in an append-only format and determine locations of data write operations agnostic of input of a write location from the file system. Metadata is updated to indicate results of the file system operation.

Abstract: An interface is instantiated receiving storage requests for storing data in the software-defined storage network using an append-only storage scheme. The interface is configured to receive requests that are agnostic of interfaces and hardware-specific details of the storage devices of the software-defined storage network. A request is received at the interface, the request comprising an identifier of a data object to be stored in the software-defined storage network using the append-only storage scheme. The request is agnostic of details of the storage devices of the software-defined storage network. Responsive to receiving the request at the interface, metadata is generated for the data object indicating that the data object is an append-only object; and the request is translated to one or more instructions for storing the data object in one or more of the storage devices using the append-only storage scheme.

Abstract: A request is received at an interface configured to receive storage requests for storing data in the software-defined storage network using an append-only storage scheme. The requests include an identifier of a data object to be stored in the software-defined storage network. The requests are agnostic of interfaces and hardware-specific details of the storage devices of the software-defined storage network. A virtualization layer of the software-defined storage network accesses data indicative of space allocation for the plurality of storage devices; and policies for prioritizing performance of the software-defined storage network. Based on the data and policies, a physical storage location at the plurality of storage devices is selected for storing the data object. Metadata is generated for the data object indicating that the data object is an append-only object and mapping the physical storage location of the data object to the identifier.

Abstract: A data store is accessed that stores a collected historical record of performance metrics for input/output operations executed at a storage device that is part of a group of storage devices that are configured to provide a fault resiliency function. A performance profile is determined for the selected storage device based on selected performance metrics of the historical record. A difference between the performance profile for the storage device and a characteristic performance profile for similar storage devices is determined. When the difference exceeds a predetermined deviance threshold, selected I/O requests designated for the selected storage device are redirected to another device of the group of storage devices.

Abstract: The techniques described herein are configured to improve the remanufacturing process by waiting to rebuild selective data items stored on a storage device that is unavailable. A storage device is unavailable when it is taken offline and/or disconnected from a network. The storage device may be taken offline due to a failed component (e.g., an actuator arm, an actuator head, damage to the underlying storage media, etc.). The storage device comprises multiple independent logical units, where a logical unit is a uniquely addressable portion of a storage device that is visible and/or that is exposed to a host. Accordingly, the techniques described herein are configured to conserve resources by selectively rebuilding data items stored in logical units of an offline storage device that are not affected by a remanufacturing process implemented due to a failed component.

Abstract: A system in which a file system may operate on a volume in which the logical address extent of the volume is divided into multiple tiers, each tier providing storage having a distinct trait set by mapping the logical addresses of the volume to appropriate underlying storage systems. A volume system exposes the volume to the file system in a manner that the file system itself has awareness of the tiers, and is aware of the trait sets of each tier. The file system may thus store file system namespaces (such as directories and files) into the tiers as appropriate for the file system namespace. A provisioning system may also be provided and be configured to provision the volume to include such tiers, and if desired, to extend the tiers.

Abstract: A system in which a file system may operate on a volume in which the logical address extent of the volume is divided into multiple tiers, each tier providing storage having a distinct trait set by mapping the logical addresses of the volume to appropriate underlying storage systems. A volume system exposes the volume to the file system in a manner that the file system itself has awareness of the tiers, and is aware of the trait sets of each tier. The file system may thus store file system namespaces (such as directories and files) into the tiers as appropriate for the file system namespace. A provisioning system may also be provided and be configured to provision the volume to include such tiers, and if desired, to extend the tiers.

Abstract: Described are embodiments which allow token-based file operations. The client may request a special offload file operation that is formatted according to a file access protocol. The file operation may be an offload read operation or an offload write operation. In an offload read operation, the client requests that data be logically read from a stored file, or a portion thereof. In response, the file server provides a response that includes a token that represents the logically read data. In some embodiments, the file server may return a response with a token that represents less than all of the requested data if for some reason it cannot provide a token that represents all of the data. The token can then be used by the client in a subsequent offload write operation. In embodiments, the tokens represent immutable data that can be safely and securely used across servers and clients.