File System Containerization for Storage Capacity Limits
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
File systems impose restrictive limits on the number of files that can be stored, leading to inefficiencies in data management and potential performance issues due to the physical storage mapping and disaster recovery constraints.
Innovation Solution
The method involves containerization of logically distinct content units within a single file, allowing multiple content units to be stored in a container file, which can be accessed and managed transparently, reducing the overall number of files and enhancing storage capacity without violating file system limits.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If multiple content units are stored as separate files in the file system, then each content unit can be independently managed and accessed, but the number of files increases and reaches file system limits, reducing storage capacity
Solution Approach 1:
Multiple logically distinct content units are merged into a single container file. The system creates a container file that can hold multiple content units, each with its own content address, allowing the file system to manage fewer files while storing more data. This directly resolves the contradiction by combining multiple files into one container structure.
Solution Approach 2:
The container file serves multiple functions: it acts as a single file in the file system hierarchy while simultaneously storing multiple distinct content units. Each content unit within the container maintains its own content address and can be independently accessed, making the container file a universal structure that fulfills both file system constraints and data organization requirements.
2Quantity of substance
If the number of files in the file system is increased to store more data, then storage capacity is improved, but file system performance significantly decreases
Solution Approach 1:
By merging multiple content units into a single container file, the system reduces the total number of files that the file system must manage. This maintains file system performance by keeping the file count low while still providing the capacity to store large amounts of data through the multi-content-unit container structure.
3Reliability
If file system limits on number of files are imposed to guarantee disaster recovery, then recovery time is controlled, but storage capacity is restricted
Solution Approach 1:
The container file provides a universal structure that maintains disaster recovery capabilities while expanding storage capacity. Since the container is managed as a single file in the file system, it benefits from the file system's disaster recovery mechanisms designed for individual files, while internally it can store multiple content units, effectively increasing storage capacity without compromising recovery guarantees.
Data Source
Figure 1A~1B
Figure 2
Figure 3~4
AI summary
One embodiment of the invention is directed to the containerization of content units that are accessed using an identifier. Applicants have appreciated that file systems sometimes impose limits on the number of files that may be stored therein that are too restrictive. Thus, in one embodiment, multiple content units may be stored in a single file, called a container file, in a file system. Each content unit may have an identifier associated with it. When an accessing entity requests access to a previously-stored content unit and provides the identifier for the content unit, the identifier may be used to locate the container file in which the content unit is stored.