Storage System Namespace Locking for Reliable Startup

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Computing devices may fail to access startup data stored in storage systems, leading to incomplete startup processes and inability to provide computer-implemented services due to concurrent access issues.

Innovation Solution

The storage system locks access to storage resources by creating associations between clients and namespaces, allowing exclusive access to the client that initiated the lock request, ensuring that only authorized clients can access the startup data during the boot process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the storage system allows concurrent access to startup data by multiple clients, then the storage system utilization is improved, but the reliability of startup process deteriorates due to potential access conflicts

Engineering Contradiction:
Improvestorage system utilizationVSAvoidstartup process reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The storage system performs preliminary actions by pre-establishing namespace associations and lock mechanisms before clients attempt to access startup data. When a client requests startup data, the system checks pre-configured namespace mappings and automatically establishes exclusive locks, preventing access conflicts before they occur. This allows the system to maintain high utilization by pre-processing access permissions while ensuring reliable startup through preemptive conflict prevention.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces namespace identifiers and lock management mechanisms as intermediaries between clients and storage resources. The namespace acts as a mediator that maps clients to specific storage namespaces, while lock structures serve as intermediaries to coordinate access. This intermediary layer enables multiple clients to access the storage system concurrently without direct conflicts, as the mediator manages and distributes access rights systematically.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If the storage system implements lock mechanisms to prevent concurrent access, then the reliability of startup process is improved, but the device complexity increases due to additional lock management overhead

Engineering Contradiction:
Improvestartup process reliabilityVSAvoidlock management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the namespace management and lock management functions into a unified system. The namespace identifier serves dual purposes: it identifies the storage namespace and simultaneously acts as a lock key. When a client is associated with a namespace, the system automatically creates a lock using the namespace identifier, combining two functions into one mechanism. This reduces overall system complexity while maintaining reliable startup processes.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The lock management system operates autonomously without requiring external intervention. When a client requests access to startup data, the system automatically checks namespace associations, generates appropriate locks, and manages the locking/unlocking process without human involvement. The self-service nature of the lock mechanism simplifies operation while ensuring reliable startup through automated conflict prevention.

Inventive Principle:
Principle #25Self-service

3Reliability

If the storage system creates namespace associations for each client, then the reliability of data access is improved, but the loss of time increases due to association lookup during startup

Engineering Contradiction:
Improvedata access reliabilityVSAvoidstartup time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-establishing namespace associations between clients and storage namespaces before startup operations. Client identifiers are mapped to namespace identifiers in advance, creating a lookup table that enables rapid identification during startup. This pre-processing eliminates the need for complex real-time association determination, reducing startup time while maintaining reliable data access through pre-configured mappings.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11630591B1System and method to manage storage system for startup
Publication Date: 2023.04.18 DELL PROD LP
  • US11630591B1 patent drawing
  • US11630591B1 patent drawing
  • US11630591B1 patent drawing

AI summary

Methods and systems for managing data for startup purposes in a distributed system are disclosed. The distributed system may include any number of clients operably connected to a storage system via a connection fabric. By virtue of the connection topology, any of the clients may interact with the storage system to gain access to storage resources of the storage system. When a client is provided access to storage resources by the storage system, other clients may not be able to access the storage resources of the storage system.