File System Per-File Integrity Selection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing file systems lack flexibility in managing data integrity, as techniques like checksums and copy-on-write can reduce performance while providing increased integrity, and there is a need for a system that allows data integrity to be a selectable attribute for file system objects.

Innovation Solution

A file system where data integrity is a selectable attribute for file system objects, allowing different default settings for various objects, enabling or disabling integrity based on specific attributes, and using operations like copy-on-write and checksums accordingly.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data integrity techniques (checksums, copy-on-write) are applied to all file system objects, then data integrity is improved, but system performance deteriorates

Engineering Contradiction:
Improvedata integrityVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies data integrity techniques selectively to specific file system objects based on their attributes rather than universally. The file system evaluates each object's attributes (such as file type, sensitivity, or user-defined properties) and applies integrity measures like checksums or copy-on-write only where appropriate, leaving other objects with standard writing performance.

Inventive Principle:
Principle #3Local quality

2Reliability

If data integrity techniques are applied to file system objects, then data integrity is improved, but device complexity increases

Engineering Contradiction:
Improvedata integrityVSAvoidfile system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a dynamic attribute-based system where data integrity behavior is determined by evaluating object attributes at runtime. The file system can adaptively select and apply different integrity techniques based on the specific characteristics of each file system object, rather than using a static, one-size-fits-all approach.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the parameter of data integrity application from a fixed system-wide setting to a variable attribute of individual file system objects. By making integrity behavior a selectable attribute that can be set based on object properties, the system manages complexity through parameterization rather than structural complexity.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If uniform data integrity settings are applied to all files, then system simplicity is maintained, but adaptability to different file requirements deteriorates

Engineering Contradiction:
Improvefile-specific integrity controlVSAvoidfile system configuration
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal attribute-based framework that can handle multiple file types and integrity requirements through a single mechanism. The same attribute evaluation and selection logic applies to all file system objects regardless of their specific type or requirements, providing adaptability without requiring separate handling for each case.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS9594798B2File system with per-file selectable integrity
Publication Date: 2017.03.14 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9594798B2 patent drawing
  • US9594798B2 patent drawing
  • US9594798B2 patent drawing

AI summary

A file system uses data integrity techniques that are a selectable attribute of a file system object. Some file system objects have integrity on for various accesses, while other file system objects do not. Different default settings can be provided for different file system objects. Such a setting for a file system object can be changed to and from having integrity on. Given a file system object with an attribute, the file system provides file system operations for which the data integrity operation used on the file system object depends on this attribute. Such operations include, but are not limited to, operations for changing the attribute, creating file system objects with such attributes, providing and changing default settings for such attributes, and writing data to and reading data from files, which use different data integrity techniques based on this attribute.