Oracle International Corporation

Sun Microsystems, Inc.

Mark Shellenbaum

John Michael Harres

Darren James Moffat

Mark Maybee

Andrew M Rudoff

Lisa Week

Reza Sabdar

Michael Leroy Gerdts

Richard J Morris

Bhaskar Sarkar

Peter W Cudhea

Techniques described herein relate to systems and methods of data storage, and more particularly to automatic file site clone generation. In certain embodiments, a computing device may include receiving a selection indicating that a clone directory is visible in a head node. In response to the selection indicating that the clone directory to be visible in the head node, the computing device may include generating a snapshot of a target file system. Also, the computing device may include duplicating a directory of the target file system into the clone directory. Further, the computing device may include mapping an address of the target file system into the clone directory. The computing device may include linking the clone directory to the head node.

Automatic filesystem clone generation

An instruction is received to define or modify a permission constraint corresponding to one or more file. A period of time is determined, where the period is one during which the defined or modified permission constraint is to apply to the one or more files. It is determined that the one or more files are to be deleted following completion of the period of time. A permission-instruction data set representing the permission constraint and a flag indicating that the one or more files are to be deleted following completion of the period of time are stored in a data store. It is detected that the period of time has ended. The one or more files are deleted in response to the detection.

Just-in-time data object permission restriction and action implementation

Using a computer system, an instruction is received to define or modify a permission constraint corresponding to one or more files. A permission-instruction data set representing the permission constraint is stored in a data store. Subsequent to storing the permission-instruction data, a user request to access a particular file is intercepted. The data store is queried to determine whether any pending permission-instruction data set corresponds to the particular file. In response to the query, it is determined that the permission-instruction data set corresponds to the particular file. A permission constraint of the particular file is added or modified based on the permission-instruction data set. Based on the modified or added permission constraint, it is determined whether and/or an extent to which the user request is authorized. A response to the user request based on the determination as to whether and/or an extent to which the user request is authorized.

Just-in-time data object permission restriction

Implementations described and claimed herein provide systems and methods for dynamically masking an access control list corresponding to a file system object in response to a change mode command. In one implementation, a change mode command for a file system object to change a first mode to a second mode is received. The first mode defines a first set of access rights and the second mode defines a second set of access rights. In response to the change mode command, a mask is dynamically applied to an access control list corresponding to the file system object. The access control list has zero or more access control entries defining access permissions for the file system object. The mask modifies any of the zero or more access control entries that have access permissions that exceed the second set of access rights defined by the second mode. The access control list is preserved.

System and methods for live masking file system access control entries

Implementations described and claimed herein provide systems and methods for resumable replication. In one implementation, an interruption in a transfer between a source and a target is identified. The transfer includes a send stream generated by the source and configured for receipt by the target. The send stream includes one or more snapshots of the source. A receive checkpoint generated by the target is received at the source. The receive checkpoint indicates data successfully received into the target during the transfer prior to the interruption. The transfer is resumed based on the received checkpoint. The resumed transfer skips any of the one or more snapshots and all data in a resumable snapshot already existing on the target. A complete transfer from the source to the target is verified using a chain of custody.

Systems and methods for resumable replication

A system for providing extended file attributes is described. Logically, attributes are supported as files within the file system. In this way, the file system is augmented with an orthogonal namespace of file attributes. According, any file (including attribute files) may have an arbitrarily deep attribute tree associated with it. Access to the attribute values is via file descriptors obtained via a special attribute interface. This logical view of &ldquo;attributes as files&rdquo; allows the leveraging of existing file system interface functionality to support the construction, deletion, and manipulation of attributes.

Growing community of inventors

Westminster, CO, United States of America

Mark Shellenbaum