Modular UNIX File System Management Framework

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The variation in file systems across different operating systems, such as Windows and UNIX-based systems, poses challenges for entities that need to provide data management capabilities, requiring frequent updates and rebuilds of management software with each new distribution release, leading to prolonged maintenance times.

Innovation Solution

A modular, script-based framework that allows for rapid deployment of file system support by writing new modules for operating systems, enabling dynamic addition of newer operations and automatically discovering multiple storage stack layouts, thereby facilitating quicker support of new file systems and operating systems without the need for complete rebuilding of management entities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If management software is completely rebuilt to support a new UNIX distribution, then data management capabilities are up-to-date, but maintenance time is extended (about six months)

Engineering Contradiction:
Improvedata management capabilitiesVSAvoidmaintenance time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The management software is divided into separate modules, each handling specific file system operations. This segmentation allows individual modules to be updated without rebuilding the entire software system, reducing maintenance time from six months to a fraction of that time while maintaining up-to-date data management capabilities for new UNIX distributions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The software architecture transitions from a static, monolithic structure to a dynamic, modular structure where components can be independently updated. This enables the system to adapt to new UNIX distributions by loading appropriate modules rather than requiring complete rebuilds, significantly reducing maintenance cycles.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If management software is frequently updated to support new distributions, then data management capabilities remain current, but development effort increases due to near-continuous updating requirements

Engineering Contradiction:
Improvedata management capabilitiesVSAvoidsoftware update complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

By segmenting the software into independent modules with well-defined interfaces, the system can selectively update only the necessary components for each new distribution. This reduces development complexity compared to managing frequent updates of a monolithic system, as each module can be developed and tested independently.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The modular architecture creates universal interfaces that work across multiple UNIX distributions. A single module can serve multiple file system types and distributions, reducing the overall number of updates needed and simplifying the development process while maintaining broad compatibility.

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

Data Source

PatentUS10310945B2Data management of UNIX file systems
Publication Date: 2019.06.04 NETAPP INC
  • US10310945B2 patent drawing
  • US10310945B2 patent drawing
  • US10310945B2 patent drawing

AI summary

Exemplary embodiments relate to techniques that allow for file system support to be rapidly deployed for new or updated operating system distributions. In some embodiments, a management component is provided perform data management on file systems. When a data management operation on a file system is requested, an operation component searches in a predetermined location for a named module that implements certain types of operations. The operation component then calls these operations (including validate, build and deport operations for the file system) to implement data management procedures in the file system. Implementing support for a new operating system or file system does not require that the management entity be rebuilt. Upon release of a new operating system or file system, a new named module can be written and placed in the predetermined location where the operation module is configured to search.