Abstract: A method for storing data, the method comprising receiving, by an offload component in a client application node, a request originating from an application executing in an application container on the client application node, wherein the request is associated with data and wherein the offload component is located in a hardware layer of the client application node, and processing, by the offload component, the request by a file system (FS) client and a memory hypervisor module executing in a modified client FS container on the offload component, wherein processing the request results in at least a portion of the data in a location in a storage pool.

Abstract: A method for deduplicating data comprising: obtaining, from a metadata node and by file system client executing on a client application node, a data layout; generating, by the client application node, a fingerprint for the data stored on the client application node; generating, by a memory hypervisor module executing on the client application node, at least one input/output (I/O) request specifying a location in a storage pool, wherein the location is determined using the data layout; issuing, by the memory hypervisor module, the at least one I/O request to the storage pool, wherein processing the at least one I/O request results in at least a portion of the data being stored at the location; and after issuing the at least one I/O request to the storage pool, transmitting the fingerprint to the metadata node, wherein the metadata node attempts to deduplicate the data using the fingerprint.

Abstract: A method for processing requests, the method comprising: receiving, from a client application node and by a metadata node, a request for a data layout, determining a QoS tag associated with the request, identifying at least one file system block (FSB) in a sparse virtual space, wherein the FSB is mapped to a location in a storage pool that is associated with the QoS tag, generating the data layout based on the at least one identified FSB; and providing the data layout to the client application, wherein the client application node uses the data layout to directly write data to the location in the storage pool, wherein the metadata node does not participate in the writing of the data to the location in the storage pool.

Abstract: A method for storing data, comprising: obtaining, from a metadata node and by file system client executing on a client application node, a data layout, generating, by the client application node, an error detection value (EDV) for the data stored on the client application node; generating, by a memory hypervisor module executing on the client application node, at least one input/output (I/O) request specifying a location in a storage pool, wherein the location is determined using the data layout; issuing, by the memory hypervisor module, the at least one I/O request to the storage pool, wherein processing the at least one I/O request results in at least a portion of the data being stored at the location; and after issuing the at least one I/O request to the storage pool, transmitting the EDV to the metadata node, wherein the metadata node stores the EDV.

Abstract: A method for storing data, comprising receiving, by an offload component in a client application node, a first request from a client translation and bridging container, wherein the client translation and bridging container translates a second request originating from an application executing in an application container on the client application node to the first request, wherein the second request is specified using object semantics and the first request is specified using file semantics, wherein the first request is associated with data, and wherein the offload component is located in a hardware layer of the client application node; and processing, by the offload component, the first request by a file system (FS) client and a memory hypervisor module executing in a modified client FS container on the offload component, wherein processing the first request results in at least a portion of the data in a location in a storage pool.

Abstract: A method for securing data, the method including obtaining, from a metadata node and by file system (FS) client executing on a client application node, a data layout and an encryption key, encrypting, by the client application node, the data stored on the client application node using the encryption key to obtain encrypted data, generating, by a memory hypervisor module executing on the client application node, at least one input/output (I/O) request, wherein the at least one I/O request specifies a location in a storage pool, wherein the location is determined using the data layout, and issuing, by the memory hypervisor module, the at least one I/O request to the storage pool, wherein processing the at least one I/O request results in at least a portion of the encrypted data being stored at the location.

Abstract: A method for managing client resources by receiving a desired load factor representing the number of instructions being executed per second (IOPS) to implement an application on a set of cores of a client device, based on the desired load factor and a latency factor, determining a maximum number of IOPS that can be executed by the cores of the client device before reaching system saturation, determining a pattern of the IOPS being executed on the set of cores based on historical IOPS information for the latency factor, and based on the historical IOPS information, determining to execute the IOPS on a subset of the set of cores.

Abstract: A method for accessing data where the method includes receiving, by an access client executing in user space, a request to read data that includes a file system identifier and an offset, identifying a storage server associated with the data, generating a command to copy the data to memory, and sending the command to the storage server.

Abstract: A method for managing file systems includes receiving, by a unified namespace manager, a first message that indicates a new file system has been created on a first node, performing an update on a top level file system namespace to include a reference to the new file system to generate an updated top level file system namespace, generating, based on the update, a second message that indicates the top level file system namespace has been updated, and sending, to a second node, the second message.

Abstract: A method for managing nodes includes detecting, by a failover node, a failure of a primary node, based on the detecting, updating a sparse virtual space to indicate that a file system previously local to the primary node is now local to the failover node, wherein the sparse virtual space is managed by a file system container executing on the failover node, and initiate execution of an instance of an application on the failover node, wherein a second instance of the application was previously executing on the primary node, and wherein the instance of the application uses the file system.

Abstract: A system for managing file systems includes memory. The system also includes a manager. The memory is used for storing in-memory data structures. The manager obtains file system references for a file system from a file system manager. The file system manager utilizes storage to provide the file system references. The manager stores the file system references in an in-memory data structure in the memory. To service file system reference requests, the manager utilizes uses the in-memory data structure to service at least one of the file system reference requests.

Abstract: A method for managing data includes obtaining, by a hypervisor on a host computing device, a write request for storing first data, and in response to the write request: identifying a first set of memory segments associated with the first data using a memory mapper, wherein the first set of memory segments is associated with a memory device, making a first determination that the memory device is local to the host computing device, and in response to the first determination: storing the first data in the first set of memory segments.

Abstract: A method for managing file systems, includes receiving, by a processor coordinator, a first operation request, identifying a file system associated with the first operation request, making a first determination that the file system is local, and in response to the first determination identifying a core thread pool associated with the file system, and directing operation of the first operation request to be executed on a core associated with the core thread pool, wherein the core is associated with a processor.

Abstract: A method for storing transaction records includes receiving, by a transaction log manager, a first commit request for a first transaction record from a first core, copying, based on the first commit request, the first transaction record to a first region of memory, making a first determination that the first region surpasses a space threshold, and copying, based on the first determination, a first plurality of transaction records from the first region to storage, wherein the first plurality of transaction records comprises the first transaction record.

Abstract: A method for moving data includes identifying, by a staging manager in a container, a trigger condition associated with data being used by an application external to the container, performing an analysis on the trigger condition, making a first determination, based on the analysis, that the trigger condition is satisfied, and processing, based on the first determination, a data movement action.

Abstract: A method, computer program product, and computing system for locally processing a plurality of data files stored on a local data storage system to effectuate the storage of one or more archivable files at one or more defined remote addresses on a remote data storage system. One or more identifiers, that locate the one or more archivable files at the one or more defined remote addresses on the remote data storage system, are stored on the local data storage system. A local database, that defines the one or more identifiers, is maintained on the local data storage system.

Abstract: A method for processing requests includes receiving a request comprising a virtual address, wherein the request is associated with an application executing on an operating system, identifying, based on data specified in the request, a logical volume associated with the data, making a first determination, based on the logical volume, that the logical volume is managed by a remote node, generating a data layout request to receive a data layout of the data from the remote node, receiving the data layout, wherein the data layout specifies a first physical address on the remote node that stores the data, initiating a copy request to copy the data from the first physical address to a second physical address on a local node, generating, based on the copy request, a virtual-to-physical address mapping between the virtual address and the second physical address; and initiating processing the request using the virtual-to-physical address mapping.

Abstract: Techniques are presented for dynamically allocating memory between containers.

Abstract: A data storage system operates a file system as a thinly provisioned file system having a host-visible virtual space and a smaller allocated space of underlying physical storage from a pool. The file system applies formatting to the allocated space and utilizes formatted allocated space for storing host files. The file system receives a file I/O request that requires increasing the allocated space of the file system, and in response (1) obtains an extent of physical storage from the pool and adds it to the file system as added allocated space, and (2) formats an initial portion of the added allocated space and satisfies the file I/O request using the formatted initial portion. Over a subsequent period the file system incrementally formats additional portions of the added allocated space and satisfies subsequent file I/O requests from the added portions.

Abstract: A method for accessing data where the method includes receiving, by an access client executing in user space, a request to read data that includes a file system identifier and an offset, identifying a storage server associated with the data, generating a command to copy the data to memory, and sending the command to the storage server.