Abstract: A system for facilitating upload file optimization via transaction transformation. A request is received for an operation to upload a file to the cloud. The system bypasses a transaction processing (sub)system and attempts to upload the file to a staging area of the cloud. When the upload transaction is ready to be executed, the system determines an upload status of the file. The system transfers the file from the staging area to an intended destination if the file has been uploaded to the staging area. If the file is not yet uploaded to the staging area, the system determines if an upload operation failed. If an upload operation did not fail, the system waits for the upload to finish prior to transferring the file to the intended destination. If the upload operation did fail, the system uploads the file to the intended destination. Once the file is transferred to the intended destination, the transaction may be marked as complete in the journal.

Abstract: A system and methods for presenting a hybrid cloud cache as a file system. The system implements a set of standard file system command line interfaces that present the objects stored by the hybrid cloud cache to users of the system as if the users were viewing and interacting with a traditional file system. The system provides an interactive shell to the users to view the contents of the hybrid cloud cache. The system may be configured to operate on a live instance as well as on an on-disk structure of the hybrid cloud cache. The system may provide the ability to present partially cached cloud data as a file system via the interactive shell for the purposes of development, support, and troubleshooting.

Abstract: A system and methods for enhancing content collaboration by conflict detection and resolution. A hybrid cloud cache receives a request from a client to upload an object to the cloud. The hybrid cloud cache may perform an internal lookup to find the latest version of the object known to it. This lookup may return a local identifier or a cloud identifier. The cache may compare a client-provided identifier to the local identifier or to the cloud identifier that is mapped to the local identifier to determine if the client-provided identifier refers to the latest uploaded version of the object. The system may determine that a conflict exists if the client-provided identifier does not match either identifier. The system may generate an alternate name for the object and upload the renamed object to the cloud from the hybrid cloud cache.

Abstract: A system and methods for presenting a hybrid cloud cache as a file system. The system implements a set of standard file system command line interfaces that present the objects stored by the hybrid cloud cache to users of the system as if the users were viewing and interacting with a traditional file system. The system provides an interactive shell to the users to view the contents of the hybrid cloud cache. The system may be configured to operate on a live instance as well as on an on-disk structure of the hybrid cloud cache. The system may provide the ability to present partially cached cloud data as a file system via the interactive shell for the purposes of development, support, and troubleshooting.

Abstract: A system for effectively addressing the fast-producer and slow-consumer problem for persistent hybrid cloud caches. In particular, the system and associated methods ensure the integrity of data stored by persistent caches by utilizing a plurality of journals, including a user journal and a cloud journal. The user journal records operations conducted by users of the system in records. Before the records are transferred to a cloud storage system, the records are transferred to the cloud journal, which may be configured to be larger than the user journal. Once a record is transferred from the user journal to the cloud journal, the record may be released from the user journal, thereby increasing capacity of the user journal for subsequent operations to be recorded. Each record may then be transferred to the cloud storage system from the cloud journal, which may then cause each record to be released from the cloud journal.

Abstract: A system for handling Implicit transactions in a hybrid cloud cache. The hybrid cloud cache maintains folders in a metadata file system that includes a hierarchy of cached folders, and maintains a meta-file containing metadata of files and folders. The system obtains a meta-file from a cloud platform and compares that to a meta-file obtained from the hybrid cloud cache. An object associated with an Implicit metadata transaction is transferred to an internal namespace of the hybrid cloud cache if the comparison indicates that certain conditions are met. The system may perform a bottom-up traversal of the namespace and may abort the traversal if an outstanding explicit transaction for the object is present or the object exists in the cloud platform. An object may be moved to a temporary storage location if there is no explicit transaction on it and the object does not exist in the cloud platform.

Abstract: A system for facilitating upload file optimization via transaction transformation. A request is received for an operation to upload a file to the cloud. The system bypasses a transaction processing (sub)system and attempts to upload the file to a staging area of the cloud. When the upload transaction is ready to be executed, the system determines an upload status of the file. The system transfers the file from the staging area to an intended destination if the file has been uploaded to the staging area. If the file is not yet uploaded to the staging area, the system determines if an upload operation failed. If an upload operation did not fail, the system waits for the upload to finish prior to transferring the file to the intended destination. If the upload operation did fail, the system uploads the file to the intended destination.

Abstract: A system for resolving transient and localized errors in a hybrid cloud cache. The system may include a subsystem within a hybrid cloud cache that provides a way to handle errors associated with uploading files or folders to a cloud. The subsystem may be used to recover files and folders created by a user that could not be pushed to the cloud, while also ensuring that metadata and data are not lost. The subsystem may work with the transaction processing subsystem of the hybrid cloud cache to facilitate the release of transactions associated with the files and folders that could not be pushed to the cloud. By doing so, the subsystem assists in unblocking subsequent transactions or user operations and allows the hybrid cloud cache to upload files and folders to the cloud without interruption.

Abstract: A system for effectively addressing the fast-producer and slow-consumer problem for persistent hybrid cloud caches. In particular, the system and associated methods ensure the integrity of data stored by persistent caches by utilizing a plurality of journals, including a user journal and a cloud journal. The user journal records operations conducted by users of the system in records. Before the records are transferred to a cloud storage system, the records are transferred to the cloud journal, which may he configured to he larger than the user journal. Once a record is transferred from the user journal to the cloud journal, the record may be released from the user journal, thereby increasing capacity of the user journal for subsequent operations to be recorded. Each record may then be transferred to the cloud storage system from the cloud journal, which may then cause each record to be released from the cloud journal.

Abstract: A system for handling Implicit transactions in a hybrid cloud cache. The hybrid cloud cache maintains folders in a metadata file system that includes a hierarchy of cached folders, and maintains a meta-file containing metadata of files and folders. The system obtains a meta-file from a cloud platform and compares that to a meta-file obtained from the hybrid cloud cache. An object associated with an Implicit metadata transaction is transferred to an internal namespace of the hybrid cloud cache if the comparison indicates that certain conditions are met. The system may perform a bottom-up traversal of the namespace and may abort the traversal if an outstanding explicit transaction for the object is present or the object exists in the cloud platform. An object may be moved to a temporary storage location if there is no explicit transaction on it and the object does not exist in the cloud platform.

Abstract: A system for resolving transient and localized errors in a hybrid cloud cache. The system may include a subsystem within a hybrid cloud cache that provides a way to handle errors associated with uploading files or folders to a cloud. The subsystem may be used to recover files and folders created by a user that could not be pushed to the cloud, while also ensuring that metadata and data are not lost. The subsystem may work with the transaction processing subsystem of the hybrid cloud cache to facilitate the release of transactions associated with the files and folders that could not be pushed to the cloud. By doing so, the subsystem assists in unblocking subsequent transactions or user operations and allows the hybrid cloud cache to upload files and folders to the cloud without interruption.

Abstract: A system and methods for presenting a hybrid cloud cache as a file system. The system implements a set of standard file system command line interfaces that present the objects stored by the hybrid cloud cache to users of the system as if the users were viewing and interacting with a traditional file system. The system provides an interactive shell to the users to view the contents of the hybrid cloud cache. The system may be configured to operate on a live instance as well as on an on-disk structure of the hybrid cloud cache. The system may provide the ability to present partially cached cloud data as a file system via the interactive shell for the purposes of development, support, and troubleshooting.

Abstract: A system and methods for grouping and executing transactions concurrently while ensuring hybrid cloud cache integrity and consistency. The system identifies upload operations in a journal and associates each such operation with an upload transaction. The upload operations may be grouped into a group of concurrently executed upload operations. If an upload transaction finishes uploading a file and there is a most recent older upload transaction having a pending upload, then the system adds the completed transaction and a dependency queue associated with that transaction to a dependency queue of the most recent older upload transaction. If the current upload transaction finishes the upload operation and the transaction has an oldest transaction identifier of the group, then the system adds a PUSHDONE record for that transaction to a hybrid cloud cache journal along with a PUSHDONE record for the other transactions depending on that completed transaction.

Abstract: The disclosed computer-implemented method for delayed allocation in cluster storage may include (i) delegating, to a node attached to a storage cluster including one or more storage devices that include a group of allocation units, a subset of allocation units on the storage cluster to be held as a delayed allocation pool, (ii) receiving, from the node, a request to allocate allocation units on the storage cluster, (iii) deducting the number of allocation units from available allocation units in the delayed allocation pool, (iv) satisfying the allocation request by allocating allocation units not in the delayed allocation pool before allocating allocation units included in the delayed allocation pool, and (v) recalculating, based on the number of allocation units in the delayed allocation pool used to satisfy the allocation request, the number of available allocation units in the delayed allocation pool. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: A computer-implemented method for performing copy-on-write operations may include (1) identifying a write operation addressed to at least a part of a storage area on a storage system, (2) determining that the storage area is configured to be copied before writing to the storage area in order to preserve original data stored within the storage area, (3) identifying an interface for offloading copy-on-write operations to the storage system, and (4) using the interface to instruct the storage system to create a copy of the storage area modified with the write operation. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: Techniques for implementing an adaptive data access error handling policy are disclosed. In one particular exemplary embodiment, the technique may be realized as a system comprising a shared storage device communicatively coupled to a network, and a computer cluster communicatively coupled to the network, the computer cluster comprising a plurality of nodes each mounting a shared file system thereon, a first node of the plurality of nodes to send a data access request to the shared storage device, to identify a data access error associated with the data access request, and to determine whether to permit access to the shared file system based on the data access error being a local data access error or a global data access error.