Unified Namespace for NAS Cluster File System Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current solutions for managing file systems in network-attached storage (NAS) clusters are cumbersome, especially for large systems with hundreds of NAS servers, as they require individual snapping and exporting of file systems, leading to complexity and error-prone processes.

Innovation Solution

The method involves operating a set of physical computing machines as a NAS cluster with first and second NAS servers, where the first server acts as an initial client access point using one protocol and the second server provides translated access using another protocol, enabling network clients to access network shares through a referral response, thus simplifying the management of client access to a namespace.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If individual file systems are snapped and exported manually in traditional NAS systems, then each file system can be managed independently, but the management process becomes cumbersome and error-prone when dealing with large systems containing hundreds of NAS servers and numerous file systems

Engineering Contradiction:
Improvefile system management operationVSAvoidmanagement process complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent merges multiple individual file system management operations into a single unified namespace management operation. By creating a unified namespace that aggregates file systems across multiple NAS servers, administrators can manage hundreds of file systems through a single interface and operation set, rather than individually managing each file system across numerous servers.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The unified namespace acts as an intermediary layer between clients and the underlying distributed file systems. This namespace abstraction layer simplifies client access by providing a single access point, while the system automatically handles the complexity of routing requests to the appropriate underlying file systems across multiple NAS servers.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If a unified namespace approach is implemented across multiple NAS servers, then client access is simplified and scalability is improved, but protocol translation complexity increases between different NAS protocols

Engineering Contradiction:
Improveclient access adaptabilityVSAvoidprotocol translation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The unified namespace is designed to support multiple NAS protocols (NFS and CIFS/SMB) simultaneously through a single access point. The namespace layer provides protocol-agnostic file access operations, while the underlying servers handle protocol-specific implementations, allowing the system to serve diverse clients with different protocol requirements through a universal interface.

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

Solution Approach 2:

The unified namespace serves as a protocol translation intermediary, receiving client requests in one protocol format and automatically translating them to the appropriate protocol for the target file system. This mediation layer handles protocol conversion transparently, allowing clients to access file systems regardless of the underlying protocol without requiring clients to understand protocol differences.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Quantity of substance

If multiple NAS servers host file systems in a unified namespace, then system capacity and scalability are improved, but performance bottlenecks may occur due to coordination overhead

Engineering Contradiction:
Improvestorage capacityVSAvoidaccess performance
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The unified namespace is segmented into multiple independent file system backends hosted on different NAS servers. Each file system maintains its own metadata and data structures, allowing independent access and minimizing coordination overhead. The namespace layer provides a unified view while the underlying segmented structure enables parallel access to different file systems without blocking other operations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by pre-establishing the unified namespace structure and mapping relationships between namespace entries and underlying file systems before client access occurs. This pre-configuration allows the system to quickly route client requests to the appropriate file systems without requiring real-time coordination or dynamic discovery, improving access performance while maintaining scalability.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10552072B1Managing file system namespace in network attached storage (NAS) cluster
Publication Date: 2020.02.04 EMC IP HLDG CO LLC
  • US10552072B1 patent drawing
  • US10552072B1 patent drawing
  • US10552072B1 patent drawing

AI summary

A technique for managing data storage provides multiple physical computing machines and block storage arranged in a NAS (network attached storage) cluster. The physical computing machines run NAS servers, with each NAS server including an FSDB (file system database) that identifies a set of file systems that belong to the NAS server. LUNs (Logical UNits) in the block storage provide backing store for the set of file systems of each NAS server. The NAS cluster manages access to a file system namespace for a set of file systems, including for example Distributed File System (DFS) typically accessed using the Server Message Block (SMB) protocol, by clients of different types, including for example clients using the Network File System (NFS) protocol.