Netapp, Inc.

Network Appliance, Inc.

Google Inc.

Paul Christopher Eastham

David A Grunwald

Emmanuel Ackaouy

Robert M English

Jason Ansel Lango

Ashish Prakash

Kartik Ayyar

Brian Mederic Quirion

Matthew Benjamin Amdur

Robert Lieh-Yuan Tsai

Dianne K Hackborn

Qinghua Zheng

Peter Griess

Meghan Desai

J Chris Wagner

Ling Zheng

George Cabrera, Iii

John K Edwards

Atul Goel

Stephen Lee Manley

Ram Kesavan

Raymond C Chen

Amith Yamasani

Szu-Wen Kuo

Yong Cho

James J Voll

J Christopher Wagner

Steven H Rodrigues

Sreelatha Sunkara Reddy

Nahush Mahajan

Robert Leih-Yuan Tsai

Christopher J Wagner

The disclosed technology includes techniques for preserving battery life of a mobile device by monitoring a mobile device to determine a state of inactivity. A state of inactivity may be determined if the screen of the mobile device is off and the mobile device remains stationary for a period of time. Battery life may be preserved by placing the mobile device and/or a mobile application of the mobile device into an idle state for successive idle periods separated by maintenance periods. When in an idle state, the mobile device and/or a mobile application of the mobile device may be prevented from utilizing various features or functions of the mobile device that may tend to drain the battery. The mobile device and/or mobile application may be granted temporary access to the various features and functions during the maintenance periods to temporarily allow the mobile device and/or mobile application to perform updates.

Systems and methods for extending battery life by monitoring device activity

The disclosed technology includes techniques for preserving battery life of a mobile device by monitoring a mobile application to determine a state of inactivity. An inactive mobile application may be placed in an idle state that may prevent the mobile application from utilizing one or more resources of the mobile device that may tend to drain the battery.

Systems and methods for extending battery life by monitoring mobile application activity

A network caching system has a multi-protocol caching filer coupled to an origin server to provide storage virtualization of data served by the filer in response to data access requests issued by multi-protocol clients over a computer network. The multi-protocol caching filer includes a file system configured to manage a sparse volume that 'virtualizes' a storage space of the data to thereby provide a cache function that enables access to data by the multi-protocol clients. To that end, the caching filer further includes a multi-protocol engine configured to translate the multi-protocol client data access requests into generic file system primitive operations executable by both the caching filer and the origin server.

System and method for caching network file systems

Methods, systems, and apparatus, including computer program products feature selecting a file in a distributed file system. The file is associated with a time to live derived from a path name for the file. The file is divided into a plurality of chunks that are distributed among a plurality of servers. Each chunk has a respective modification time indicating when the chunk was last modified. A latest respective modification time among the respective modification times of each of the plurality of chunks is selected. A determination is made as to whether an elapsed time based on the latest modification time is equal to or exceeds the time to live. Each of the chunks of the file is deleted responsive to the determination. Other embodiments of this aspect include corresponding systems, apparatus, and computer program products.

Automatic deletion of temporary files

A technique is disclosed for restoring data of sparse volumes, where one or more block pointers within the file system structure are marked as ABSENT, and fetching the appropriate data from an alternate location on demand. Client data access requests to the local storage system initiate a restoration of the data from a backing store as required. A demand generator can also be used to restore the data as a background process by walking through the sparse volume and restoring the data of absent blocks. A pump module is also disclosed to regulate the access of the demand generator. Once all the data has been restored, the volume contains all data locally, and is no longer a sparse volume.

System and method for restoring data on demand for instant volume restoration

A system and method for storing and retrieving file system log information in a cluster computer system is provided. In response to an aborted takeover operation, a surviving storage system stores a set of file replay log information on storage devices associated with the surviving storage system. When the failed storage system re-initializes, it retrieves the file replay log information from the surviving storage system and utilizes the file replay log information to render its disks consistent.

System and method for storing and retrieving file system log information in a clustered computer system

An architecture, including a file-level protocol, for supporting sparse volumes on a storage system is provided. The file-level protocol provides coherency checking for use in retrieving data stored on a backing store remote from a storage system.

Architecture for supporting sparse volumes

In an embodiment, a method to provide data consistency in a storage system, includes: providing, by a server to a proxy cache, a lock associated with a delegated file in the server; in response to a write request from a client, modifying data in a cached copy of the delegated file in the proxy cache; revoking, by the server, the lock associated with the delegated file, in response to a request from another device to access the delegated file so that the delegated file is now a formerly delegated file; and writing the modified data to the formerly delegated file in the server to update the formerly delegated file; and permitting access to the formerly delegated file by the another device.

Apparatus and method for data consistency in a proxy cache

A method for handling a fault in a storage system comprises maintaining data in a mass storage subsystem and providing access to the data on behalf of a client. The method further comprises detecting a fault in a volume of data stored in the mass storage subsystem, determining a severity of the fault, and selecting a course of action in response to the fault, based on the severity of the fault.

Method and apparatus for handling data corruption or inconsistency in a storage system

Systems and methods of performing lightweight fault monitoring and analysis are described. In certain embodiments, the lightweight fault monitoring and analysis system and method include a crash dump component operable to generate a lightweight core file for a machine without generating a complete core file. The lightweight core file is smaller in size than a complete core file and contains information relevant for fault monitoring and analysis. The lightweight core has a data structure portion reflecting the state of only a portion of actual working memory at the time of a problem. The lightweight core file contains both regions in memory specific to the problem encountered and some standard regions.

Creating lightweight fault analysis records

A network cache is automatically configured so that the network cache is able to communicate with a database to authenticate a user. A user ID is received as input and is used to query a database for objects having the user ID. The user object corresponding to the user ID is selected and the attributes within the user object are output to a user interface. The attribute name corresponding to the user ID is selected. Attribute names corresponding to group IDs in the user object are selected. If other forms of group membership exist, a non-parent object is retrieved and the attribute name corresponding to the group ID in the object is selected. Once each attribute name is selected the attribute name is stored in a configuration file in the network cache.

Method for autoconfiguration of authentication servers

In one embodiment, a method for providing consistent services semantics for multiple services running different instances of an application comprises maintaining, at a network node, data identifying current application versions associated with the multiple services, and selecting, at the network node, a new preferred application version based on the data identifying current application versions upon detecting a predefined event pertaining to the multiple services. The method further comprises identifying, at the network node, services that run the new preferred application version, and balancing the distribution of requests between the services that run the new preferred application version until detecting a next predefined event.

Growing community of inventors

Mountain View, CA, United States of America

Paul Christopher Eastham