Abstract: Examples include translation of a source m-node identifier (ID) to a target m-node ID, the source m-node ID identifying a source m-node representing a file system object in a source file system, and the source m-node ID including a source replication set ID, a source m-node container ID, and at least one local ID. In examples, a source m-node container ID is replaced with a target m-node container ID in the target m-node ID.

Abstract: Examples include, in response to fulfillment of a tiering policy, dividing, by a cloud provider engine of a computing device, data blocks of a filesystem object into data chunks. Some examples comprise generating, by the cloud provider engine, a current manifest file in a local memory and causing the cloud storage system to generate a current pseudo folder in the cloud storage system corresponding to a particular epoch of the filesystem object. Some other examples comprise tiering, by the cloud provider engine, the data chunks and the current manifest file to the current pseudo folder, the current manifest including pointers to the data chunks corresponding to the filesystem object at the particular epoch.

Abstract: In some examples, a system determines, based on information relating to access of objects in storage segments by requester devices, an affinity between access devices and the storage segments that are managed by respective controllers of a plurality of controllers, the access devices comprising the requester devices or the controllers. The system selects, based on the affinity between the access devices and the storage segments, a controller of the plurality of controllers for serving requests of a first requester device of the requester devices to access objects.

Abstract: A storage system includes a distributed file system. An attribute of a particular entity in the file system relates to a snapshot. In response to an operation in the storage system, it is determined whether the snapshot attribute is to be propagated to another entity of the file system.

Abstract: Examples described herein include receiving a request for a clone of a directory tree in a distributed file system for the directory tree at a first point in time. Examples described herein also include generating a copy of an inode data and determining a relevancy of the clone based on a birth epoch and a death epoch of a first entry in the inode data. The inode data may describe a root of the directory tree at a second point in time.

Abstract: In some examples, a system determines, based on information relating to access of objects in storage segments by requester devices, an affinity between access devices and the storage segments that are managed by respective controllers of a plurality of controllers, the access devices comprising the requester devices or the controllers. The system selects, based on the affinity between the access devices and the storage segments, a controller of the plurality of controllers for serving requests of a first requester device of the requester devices to access objects.

Abstract: Examples include translation of a source m-node identifier (ID) to a target m-node ID, the source m-node ID identifying a source m-node representing a file system object in a source file system, and the source m-node ID including a source replication set ID, a source m-node container ID, and at least one local ID. In examples, a source m-node container ID is replaced with a target m-node container ID in the target m-node ID.

Abstract: Examples include, in response to fulfilment of a tiering policy, dividing, by a cloud provider engine of a computing device, data blocks of a filesystem object into data chunks. Some examples comprise generating, by the cloud provider engine, a current manifest file in a local memory and causing the cloud storage system to generate a current pseudo folder in the cloud storage system corresponding to a particular epoch of the filesystem object. Some other examples comprise tiering, by the cloud provider engine, the data chunks and the current manifest file to the current pseudo folder, the current manifest including pointers to the data chunks corresponding to the filesystem object at the particular epoch.

Abstract: A storage system includes a distributed file system. An attribute of a particular entity in the file system relates to a snapshot. In response to an operation in the storage system, it is determined whether the snapshot attribute is to be propagated to another entity of the file system.

Abstract: A storage system includes a distributed file system. An attribute of a particular entity in the file system relates to a snapshot. In response to an operation in the storage system, it is determined whether the snapshot attribute is to be propagated to another entity of the file system.

Abstract: A storage system includes a distributed file system. An attribute of a particular entity in the file system relates to a snapshot. In response to an operation in the storage system, it is determined whether the snapshot attribute is to be propagated to another entity of the file system.

Abstract: A system includes storage configured to store file system entities, including directories and files, residing in segments of a distributed, segmented single file system, file servers configured to implement the single file system with separate ones of the file servers controlling metadata of separate ones of the segments, and a controller configured to control storage of files in the file system such that for a master file stored in a first segment, a first replica of the master file will be stored in a second segment that is physically separate from the first segment, the controller being further configured to control storage of directories in the file system such that a single directory will include identifiers for the master file and the first replica.