| Patent application number | Description | Published |
|---|
| 20090157770 | Live Volume Access - This document describes tools capable of enabling an entity requiring exclusive access to data and metadata of a volume to have that exclusive access while also permitting another entity to have access to data and metadata of that volume. The tools, for example, may permit a ChkDsk program to detect and correct data/metadata integrity errors while permitting users to maintain access to a live volume having that data and metadata. In one embodiment the tools create a copy of a logical volume, permit exclusive access to the copy while permitting access to the live volume, and, when the exclusive access is no longer needed, merge the copy and the live volume. | 06-18-2009 |
| 20090248757 | Application-Managed File Versioning - In accordance with one or more aspects of the application-managed file versioning, a request to store a new version of a file is received from an application, the request having been generated by the application. A filename for the new version of the file is generated, derived from a standardized naming convention. The filename includes a first portion having at least a portion of a name of the file, and a second portion having data indicating that the new version of the file is a version of the file. A set of application programming interfaces (APIs) can be exposed that allow the application to manage file versions, such as creating a new version of a file, identifying one or more versions of the file, listing one or more versions of the file, and deleting one or more versions of the file. | 10-01-2009 |
| 20090327360 | EFFICIENT FILE MANAGEMENT THROUGH GRANULAR OPPORTUNISTIC LOCKING - Improved methods and systems for granular opportunistic locking mechanisms (oplocks) are provided for increasing file caching efficiency. Oplocks can be specified with a combination of three possible granular caching intentions: read, write, and/or handle. An oplock can be specified with an identifier that indicates a client/specific caller to avoid breaking the original oplock due to an incompatibility from other requests of the same client. An atomic oplock flag is added to create operations that allow callers to request an atomic open with an oplock with a given file. | 12-31-2009 |
| 20110113077 | Extending Cluster Allocations In An Extensible File System - An extensible file system format for portable storage media is provided. The extensible file system format includes the specification of primary and secondary directory entry types that may be custom defined. The primary and secondary directory entry types can be further classified as critical and benign directory entries. The directory entry types can define whether a cluster chain corresponding to a file can be contiguously allocated. | 05-12-2011 |
| 20110113078 | Extending Cluster Allocations In An Extensible File System - An extensible file system format for portable storage media is provided. The extensible file system format includes the specification of primary and secondary directory entry types that may be custom defined. The primary and secondary directory entry types can be further classified as critical and benign directory entries. The directory entry types can define whether a cluster chain corresponding to a file can be contiguously allocated. | 05-12-2011 |
| 20110252076 | EXTENDING CLUSTER ALLOCATIONS IN AN EXTENSIBLE FILE SYSTEM - An extensible file system format for portable storage media is provided. The extensible file system format includes the specification of primary and secondary directory entry types that may be custom defined. The primary and secondary directory entry types can be further classified as critical and benign directory entries. The directory entry types can define whether a cluster chain corresponding to a file can be contiguously allocated. | 10-13-2011 |
| 20120102272 | EFFICIENT FILE MANAGEMENT THROUGH GRANULAR OPPORTUNISTIC LOCKING - Improved methods and systems for granular opportunistic locking mechanisms (oplocks) are provided for increasing file caching efficiency. Oplocks can be specified with a combination of three possible granular caching intentions: read, write, and/or handle. An oplock can be specified with an identifier that indicates a client/specific caller to avoid breaking the original oplock due to an incompatibility from other requests of the same client. An atomic oplock flag is added to create operations that allow callers to request an atomic open with an oplock with a given file. | 04-26-2012 |
| 20120159243 | Proactive Error Scan And Isolated Error Correction - Processing for file system volume error detection and processing for resultant error correction are separated to support system availability and user satisfaction. File system volumes for storing data structures are proactively scanned while the volumes remain online to search for errors or corruptions thereon. Found errors are scheduled to be corrected, i.e., spot corrected, dependent on the severity of the identified errors, error correction scheduling and/or at the determination of a file system administrator and/or user, to assist in maintaining minimal user and file system impact. When spot correction is initialized, one file system volume at a time is taken offline for correction. Spot correction verifies prior logged corruptions for the offline volume, and if independently verified, attempts to correct the prior noted corruptions. Volumes are retained offline only for the time necessary to verify and attempt to correct prior noted volume corruptions. | 06-21-2012 |
| 20120159255 | Online Fault Verification In A File System - Data structure errors, or corruptions, identified during, e.g., normal computing device system processing, file system processing or user access processing, are verified prior to the file system identifying the error for offline correction or notifying the user or system administrator a data structure error exists. Identified data structure corruptions are verified while the file system volumes are maintained online and otherwise accessible to other processing tasks and user access. Verified data structure corruptions are logged for further corrective processing. Data structure corruptions that cannot be verified, i.e., false positives, are not further processed and are not identified to file system administrators or users as corruptions, freeing the file system to concentrate on normal processing and true, verifiable errors. | 06-21-2012 |
| 20120159256 | File System Resiliency Management - Perceived corruptions encountered on file system volumes, and which cannot be initially remedied online, are processed to verify whether they are true, existing volume data structure corruptions or, alternatively, false positives. Upon the verification of one or more of a volume's corruptions, error scanning is performed to check for, and attempt to remedy online, all the existing corruptions on the volume. Subsequent to error scanning processing, if one or more verified corruptions continue to exist on a file system volume, at file system boot up time spot corruption correction is performed to attempt to remedy the existing, verified corruptions on the volume. Spot corruption correction is performed to attempt to correct verified data structure corruptions on a volume of the file system while the volume is maintained offline for the time necessary to attempt to correct its prior identified corruptions. | 06-21-2012 |
| 20130073819 | EFFICIENT FILE SYSTEM METADATA SCANNING USING SCOPED SNAPSHOTS - Volumes of a file system remain online, and thus available for use, while being proactively error scanned for corruptions thereon. A snapshot of each volume being proactively error scanned is maintained for the volume during the proactive error scanner processing of the volume. Proactive error scanner processing only requires access to tile system metadata to correctly process a volume for an identification of the corruptions thereon, and thus, a snapshot of the entire volume nerd not be generated nor maintained. The clusters of a volume that store file system metadata are identified and only these clusters are maintained in a scoped snapshot for the volume during proactive error scanning of the volume. | 03-21-2013 |
| 20130246486 | EXTENDING CLUSTER ALLOCATIONS IN AN EXTENSIBLE FILE SYSTEM - An extensible file system format for portable storage media is provided. The extensible file system format includes the specification of primary and secondary directory entry types that may be custom defined. The primary and secondary directory entry types can be further classified as critical and benign directory entries. The directory entry types can define whether a cluster chain corresponding to a file can be contiguously allocated. | 09-19-2013 |
| 20130262379 | EXTENDING CLUSTER ALLOCATIONS IN AN EXTENSIBLE FILE SYSTEM - An extensible file system format for portable storage media is provided. The extensible file system format includes the specification of primary and secondary directory entry types that may be custom defined. The primary and secondary directory entry types can be further classified as critical and benign directory entries. The directory entry types can define whether a cluster chain corresponding to a file can be contiguously allocated. | 10-03-2013 |
