In some examples, a system may determine a mountpoint included in a first filesystem for mounting a userspace filesystem. For instance, the userspace filesystem may be executable in a userspace provided by an operating system. The system may determine a bind mount path for a mount path corresponding to the mountpoint. The system may bind mount, to the determined bind mount path, at least a portion of a second filesystem associated with the mount path corresponding to the mountpoint. In addition, the system may mount the userspace filesystem at the mountpoint, and may incorporate data from the second filesystem into the userspace filesystem through the bind mount path.

In some examples, a system may determine a mountpoint included in a first filesystem for mounting a userspace filesystem. For instance, the userspace filesystem may be executable in a userspace provided by an operating system. The system may determine a bind mount path for a mount path corresponding to the mountpoint. The system may bind mount, to the determined bind mount path, at least a portion of a second filesystem associated with the mount path corresponding to the mountpoint. In addition, the system may mount the userspace filesystem at the mountpoint, and may incorporate data from the second filesystem into the userspace filesystem through the bind mount path.

A method is provided, comprising: receiving, from a host device, a request to create a token that represents one or more data items that are stored in a first volume, the first volume being stored in a source system; estimating an I/O latency limit for the first volume; estimating a token creation time for the token; comparing the token creation time to the I/O latency limit; when the token creation time matches the I/O latency limit: creating the token, creating a snapshot pair, mapping the token to the snapshot pair, and returning the token to the host device; when the token creation time does not match the I/O latency limit: creating the token, creating a first snapshot of the first volume at the source system, mapping the first snapshot to the token, and returning the token to the host device.

A method is provided, comprising: receiving, from a host device, a request to create a token that represents one or more data items that are stored in a first volume, the first volume being stored in a source system; estimating an I/O latency limit for the first volume; estimating a token creation time for the token; comparing the token creation time to the I/O latency limit; when the token creation time matches the I/O latency limit: creating the token, creating a snapshot pair, mapping the token to the snapshot pair, and returning the token to the host device; when the token creation time does not match the I/O latency limit: creating the token, creating a first snapshot of the first volume at the source system, mapping the first snapshot to the token, and returning the token to the host device.

Performing data synchronization is disclosed, including: receiving an indication to synchronize a container to a snapshot, wherein the container has a first data state and an identity, wherein the snapshot corresponds to a second data state; causing the container to have the second data state corresponding to the snapshot; and maintaining the identity of the container.

Systems and methods are provided for using a file-sharing service to identify, execute, and provide continuing access to remote computer programs. In certain embodiments, a list of files to be accessed remotely is provided to a first device, a selection is received from a user at the first device identifying a file from the provided list, and an application is executed on a second device to access a copy of the identified file, which is synchronized with a file-sharing service.

In one example, a catalog service may use a peer-to-peer network to distribute a data content item across multiple associated user devices. The catalog service may maintain a device group list describing a device group and a content catalog for the device group listing a data content set stored in the device group. The catalog service may identify a content change to the data content set listed in the content catalog at a seed device of the device group. The catalog service may send an update alert to a leeching device of the device group of the content change to trigger the leeching device to receive the content change over a peer-to-peer network between the seed device and the leaching device.

Peer-to-peer redundant file server system and methods include clients that determine a target storage provider to contact for a particular storage transaction based on a pathname provided by the filesystem and a predetermined scheme such as a hash function applied to a portion of the pathname. Servers use the same scheme to determine where to store relevant file information so that the clients can locate the file information. The target storage provider may store the file itself and/or may store metadata that identifies one or more other storage providers where the file is stored. A file may be replicated in multiple storage providers, and the metadata may include a list of storage providers from which the clients can select (e.g., randomly) in order to access the file.

A synchronization queuing service associated with a content management system repository can record file events occurring to content items maintained at the content management system repository. The synchronization queuing service can receive a file synchronization request for information identifying a content item to which a client machine is subscribed. The synchronization queuing service can determine consistency or inconsistency of a client machine state of the content item relative to the content item at the content management system repository and can respond to client machine with a file event summary comprising information usable by the client machine to identify actions necessary to synchronize the client machine state of the content item the content item.

This disclosure describes techniques performing data object renaming operations. This disclosure describes techniques for performing data object renaming operations in a manner that may reduce file system corruption and data loss. The techniques described herein may include selectively journaling particular types of renaming operations. Selectively journaling particular types of renaming operations may mitigate potential data loss and file system corruption.