Abstract: A system and method for designating and administering authority in a trusted environment is provided. In some embodiments, a determination is made that a transfer of the authority to a second computing entity is warranted. The second computing entity is opportunistically contacted, and during the opportunistic contact, the authority is passed from the first computing entity to the second computing entity. The passing of the authority from the first computing entity to the second computing entity tasks the second computing entity with updating members of the group of the passing of the authority. The passing of authority may include providing an outstanding group update to the second computing entity and may also include tasking the second computing entity with completing the outstanding group update.

Abstract: A system and method for designating and administering authority in a trusted environment is provided. In some embodiments, a determination is made that a transfer of the authority to a second computing entity is warranted. The second computing entity is opportunistically contacted, and during the opportunistic contact, the authority is passed from the first computing entity to the second computing entity. The passing of the authority from the first computing entity to the second computing entity tasks the second computing entity with updating members of the group of the passing of the authority. The passing of authority may include providing an outstanding group update to the second computing entity and may also include tasking the second computing entity with completing the outstanding group update.

Abstract: Access to objects of a computing environment is managed. Access to an object of the computing environment is prohibited via one cached entity corresponding to the object, while access to the object is allowed via another cached entity. The cached entities are concurrently maintained for a period of time, but the one cached entity is in a shadow state. In one example, the cached entities are session locks and the object is a file system object.

Abstract: Facilitating error handling of computing environments, including those environments having file systems. Responsive to an entity of the computing environment, such as a client of a file system, obtaining at least an indication of an error, a portion of functionality of the entity is automatically frozen. The obtaining is, for instance, responsive to an event of another entity of the computing environment, such as a server of the file system. Eventually, the frozen functionality is thawed allowing the functionality to proceed.

Abstract: Improved techniques are disclosed for accessing content in file systems, allowing file system clients to realize advantages of file system referrals even though a file access protocol used by the client is not specifically adapted for referral objects. (For example, the client may have a legacy file system protocol or a proprietary file system protocol which does not support referrals.) These advantages include a uniform name space view of content in a network file system, and an ability to locate content in a (nearly) seamless and transparent manner, even though the content may be dynamically moved from one location to another or replicated in different locations. A file system server returns a symbolic link in place of a referral, and an automated file mounting process on the client is leveraged to access the content using the link. Built-in crash recovery techniques of the file system client are leveraged to access moved content.

Abstract: A method and system for replicating a file system organized as a data structure from a source server to a target server. The replication process preserves the order of the inode table entries from the source file system to in the target file system at all stages of the replication process, as well as the internal consistency of the replica of the data structure on the target server. This replication eliminates use and employment of a map as the order of the inode index is preserved during the replication process.

Abstract: A buffer of block addresses for use by a client for read and write operations in a client-server system is maintained. Block addresses are maintained in the buffer and are streamed to the client in response to a request for the addresses to support a read or write operation. The quantity of addresses maintained in the buffer may be dynamically adjusted in response consumption of addresses for read and write operations.

Abstract: A method and system for managing availability of a dependent thread to service a nested request is provided. A plurality of reply threads are maintained in a single thread pool. In addition, a counter is provided to track availability of a reply thread from the thread pool. A service thread that requires at least one reply thread to complete execution of a request must check the counter to determine availability of the reply thread prior to execution of the request. The process of determining availability of a reply thread prior to execution of a service thread request avoids initiating execution of a request that cannot be completed in a timely manner, or at all.

Abstract: Facilitating error handling of computing environments, including those environments having file systems. Responsive to an entity of the computing environment, such as a client of a file system, obtaining at least an indication of an error, a portion of functionality of the entity is automatically frozen. The obtaining is, for instance, responsive to an event of another entity of the computing environment, such as a server of the file system. Eventually, the frozen functionality is thawed allowing the functionality to proceed.

Abstract: Facilitating error handling of computing environments, including those environments having file systems. Responsive to an entity of the computing environment, such as a client of a file system, obtaining at least an indication of an error, a portion of functionality of the entity is automatically frozen. The obtaining is, for instance, responsive to an event of another entity of the computing environment, such as a server of the file system. Eventually, the frozen functionality is thawed allowing the functionality to proceed.

Abstract: According to one embodiment, a method is disclosed herein that includes creating a flashcopy of initial replica data, performing a recovery of the created flashcopy, and exporting the recovered flashcopy. In one implementation, the method includes determining whether the initial replica data has changed data, generating an updated flashcopy based on the determination, sequentially quiescing an export of the recovered flashcopy, switching the recovered flashcopy with the updated flashcopy, and exporting the switched flashcopy.

Abstract: Access to objects of a computing environment is managed. Access to an object of the computing environment is prohibited via one cached entity corresponding to the object, while access to the object is allowed via another cached entity. The cached entities are concurrently maintained for a period of time, but the one cached entity is in a shadow state. In one example, the cached entities are session locks and the object is a file system object.

Abstract: Access to objects of a computing environment is managed. Access to an object of the computing environment is prohibited via one cached entity corresponding to the object, while access to the object is allowed via another cached entity. The cached entities are concurrently maintained for a period of time, but the one cached entity is in a shadow state. In one example, the cached entities are session locks and the object is a file system object.

Abstract: A buffer of block addresses for use by a client for read and write operations in a client-server system is maintained. Block addresses are maintained in the buffer and are streamed to the client in response to a request for the addresses to support a read or write operation. The quantity of addresses maintained in the buffer may be dynamically adjusted in response consumption of addresses for read and write operations.

Abstract: Improved techniques are disclosed for accessing content in file systems, allowing file system clients to realize advantages of file system referrals even though a file access protocol used by the client is not specifically adapted for referral objects. (For example, the client may have a legacy file system protocol or a proprietary file system protocol which does not support referrals.) These advantages include a uniform name space view of content in a network file system, and an ability to locate content in a (nearly) seamless and transparent manner, even though the content may be dynamically moved from one location to another or replicated in different locations. A file system server returns a symbolic link in place of a referral, and an automated file mounting process on the client is leveraged to access the content using the link. Built-in crash recovery techniques of the file system client are leveraged to access moved content.

Abstract: A system provides referencing from one file system server to another through the use of a file system location database, improving movement and replication of file systems. When a file system is moved from a first file system server, a data object that references the file system remains in the first server and contains information used to find the current location of the file system. The actual location of the file system is stored in the separate file system location database, which contains the locations of file systems on a number of file system servers. This allows the data in a file system to be replicated or moved without requiring updates to the data in any redirecting or referencing servers.

Abstract: Facilitating error handling of computing environments, including those environments having file systems. Responsive to an entity of the computing environment, such as a client of a file system, obtaining at least an indication of an error, a portion of functionality of the entity is automatically frozen. The obtaining is, for instance, responsive to an event of another entity of the computing environment, such as a server of the file system. Eventually, the frozen functionality is thawed allowing the functionality to proceed.

Abstract: Improved techniques are disclosed for accessing content in file systems, allowing file system clients to realize advantages of file system referrals even though a file access protocol used by the client is not specifically adapted for referral objects. (For example, the client may have a legacy file system protocol or a proprietary file system protocol which does not support referrals.) These advantages include a uniform name space view of content in a network file system, and an ability to locate content in a (nearly) seamless and transparent manner, even though the content may be dynamically moved from one location to another or replicated in different locations. A file system server returns a symbolic link in place of a referral, and an automated file mounting process on the client is leveraged to access the content using the link. Built-in crash recovery techniques of the file system client are leveraged to access moved content.

Abstract: A first file system includes a data object that references a second file system. The data object can be a new or existing file type with data identifying the second file system or some of its properties. The data required to locate the second file system is stored in a file system location data structure that may be located outside the first file system. The data object may then contain a key value, such as a name or a number, identifying the second file system, that can be used to look up the file system location. A referencing server may encode the file system identification and include the encoded file system identification rather than a path. When a server receives a request with a path that is encoded, the server decodes the file system identification. Then, the server may locate the root of the file system identified by the file system identification and return the root object to the client.