A system can establish a primary file system on a block array of computer storage, wherein the block array comprises a range of addresses, wherein the primary file system is configured to address the range of addresses. The system can establish a shadowed file system on the block array, wherein the shadowed file system is configured to access portions of the block array that are unused by the primary file system. The system can, in response to receiving a request to write data to the primary file system, and in response to determining that an amount of the block array utilized by the primary file system is full, transfer a first portion of the block array utilized by the shadowed file system to the primary file system.
Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
5. The system of claim 1, wherein the shadowed file system omits a guarantee that data written to the shadowed file system will be available at a future time.
The invention relates to a data storage system that includes a shadowed file system designed to improve performance by omitting a guarantee that data written to it will be available at a future time. The system comprises a primary file system and a shadowed file system, where the shadowed file system operates as a temporary storage layer that does not ensure data persistence. This design allows the system to prioritize speed over reliability, making it suitable for scenarios where immediate data access is critical, and long-term storage is handled separately. The primary file system maintains traditional data persistence guarantees, while the shadowed file system accelerates operations by bypassing certain consistency checks and durability mechanisms. This approach reduces latency and improves throughput for temporary or intermediate data, which may later be transferred to the primary file system for long-term storage. The system is particularly useful in environments where performance is prioritized over strict data durability, such as in caching, temporary file handling, or high-speed data processing pipelines. The shadowed file system may use volatile memory or other non-persistent storage media to further enhance speed, with the understanding that data may be lost if the system fails or is reset. This trade-off between performance and reliability allows the system to optimize resource usage while still providing a functional storage solution for non-critical or transient data.
6. The system of claim 1, wherein the primary file system guarantees that data written to the primary file system will be available at a future time.
This invention relates to a data storage system designed to ensure data durability and availability. The system includes a primary file system that guarantees data written to it will remain accessible at a future time, addressing the problem of data loss or unavailability in storage systems. The primary file system is configured to persistently store data, ensuring that once data is written, it is protected against loss and can be retrieved later. The system may also include a secondary file system that operates in conjunction with the primary file system to enhance data reliability or performance. The secondary file system may handle tasks such as caching, replication, or backup to support the primary file system's durability guarantees. The system ensures that data written to the primary file system is not only stored but also remains accessible over time, even in the event of system failures or disruptions. This is achieved through mechanisms such as write-ahead logging, checksums, or distributed replication to maintain data integrity and availability. The invention is particularly useful in environments where data durability is critical, such as enterprise storage, cloud computing, or database systems.
7. The system of claim 1, wherein the primary file system is associated with a first user account, and wherein the block array provides a first amount of storage that the first user account ordered.
This invention relates to a storage system that manages data across multiple file systems and user accounts. The system includes a primary file system linked to a first user account, which has allocated a specific amount of storage capacity. The primary file system is connected to a block array, a secondary storage structure that provides additional storage beyond the primary file system's capacity. The block array can be shared across multiple user accounts, allowing flexible storage allocation beyond individual user limits. The system dynamically manages data placement between the primary file system and the block array to optimize storage usage and performance. The primary file system handles frequently accessed data, while the block array stores less frequently accessed or archived data. The system ensures data integrity and access control by maintaining separate user accounts while allowing shared storage resources. This approach enables efficient storage utilization, cost savings, and scalable storage solutions for multi-user environments. The invention addresses the challenge of managing storage resources in systems where individual user accounts have limited storage capacity but require access to larger shared storage pools.
8. The system of claim 7, wherein the shadowed file system is configured to access a second amount of storage that the primary file system is not configured to access.
A system for managing file storage includes a primary file system and a shadowed file system. The primary file system handles standard file operations, while the shadowed file system operates in parallel to provide additional storage capabilities. The shadowed file system is configured to access a second amount of storage that the primary file system cannot access. This allows the system to utilize additional storage resources that are not available to the primary file system, enabling enhanced data management, redundancy, or capacity expansion. The shadowed file system may operate independently or in coordination with the primary file system to ensure data integrity, performance optimization, or seamless failover. The system may be used in environments where storage flexibility, scalability, or fault tolerance is required, such as in enterprise computing, cloud storage, or distributed file systems. The shadowed file system's ability to access separate storage resources ensures that the system can leverage additional storage capacity without modifying the primary file system's configuration.
10. The method of claim 9, wherein the primary file system is associated with a first user account, and wherein the block array provides a first amount of storage that the first user account ordered.
A method for managing storage in a distributed file system addresses the challenge of efficiently allocating and tracking storage resources across multiple user accounts. The system includes a primary file system associated with a first user account, which utilizes a block array to allocate storage. The block array provides a predefined amount of storage that the first user account has ordered, ensuring that the allocated storage is reserved and managed according to the user's subscription or purchase. The method involves dynamically assigning storage blocks from the block array to the primary file system as needed, while maintaining a record of the allocated blocks to prevent over-allocation or unauthorized access. This approach optimizes storage utilization by allowing flexible allocation within the user's ordered capacity, while also ensuring that the system can track and enforce storage limits. The method may also include mechanisms for monitoring usage, generating alerts when storage thresholds are approached, and adjusting allocations based on demand or policy changes. By associating storage blocks with specific user accounts and their ordered capacity, the system ensures fair and efficient resource distribution in a multi-tenant environment.
11. The method of claim 10, wherein the secondary file system is configured to access a second amount of storage that the primary file system is not configured to access.
A method for managing file systems in a computing environment involves using a primary file system and a secondary file system to optimize storage access and performance. The primary file system handles standard file operations, while the secondary file system is configured to access a separate storage resource that the primary file system cannot access. This secondary storage may include additional storage devices, networked storage, or specialized storage media not directly supported by the primary file system. By leveraging the secondary file system, the method enables access to a second amount of storage that would otherwise be unavailable to the primary file system, improving storage flexibility and capacity. The secondary file system may also be used to offload specific tasks, such as archiving, backup, or handling large datasets, to enhance overall system efficiency. This approach allows for better resource utilization and scalability in environments where storage requirements exceed the capabilities of a single file system.
12. The system of claim 9, wherein the primary file system is configured to overwrite portions of the block array that are used by the secondary file system, without involvement in the overwriting by the secondary file system.
This invention relates to a data storage system that manages multiple file systems sharing a common block storage device. The problem addressed is ensuring efficient and conflict-free access to shared storage blocks between primary and secondary file systems, particularly when the primary file system needs to overwrite blocks that the secondary file system is using. The system includes a primary file system and a secondary file system, both configured to access a shared block array. The primary file system is designed to overwrite portions of the block array that are in use by the secondary file system without requiring the secondary file system to participate in or coordinate the overwriting process. This allows the primary file system to perform necessary updates without disrupting the secondary file system's operations, while still maintaining data integrity. The secondary file system may continue to access its allocated blocks independently, even as the primary file system modifies overlapping regions of the storage. The system ensures that the secondary file system's data remains accessible and consistent despite the primary file system's modifications, avoiding the need for complex coordination mechanisms. This approach improves storage efficiency and performance by reducing overhead associated with inter-file system synchronization.
13. The method of claim 9, wherein the primary file system is configured to provide consistency, and wherein the secondary file system is not configured to provide consistency.
A method for managing file systems in a distributed storage environment addresses the challenge of balancing performance and data consistency. The method involves a primary file system and a secondary file system, where the primary file system is designed to ensure data consistency, meaning that all operations are completed in a predictable and reliable manner, preventing data corruption or loss. In contrast, the secondary file system is optimized for performance rather than consistency, allowing faster operations but without strict guarantees on data integrity. The primary file system may use mechanisms like journaling, checksums, or distributed consensus protocols to maintain consistency, while the secondary file system may prioritize speed by skipping or simplifying such checks. This approach allows systems to leverage the strengths of both file systems—reliability where needed and speed where possible—depending on the specific requirements of the application or workload. The method can be applied in scenarios such as cloud storage, database systems, or distributed computing environments where different levels of consistency are required for different operations.
14. The method of claim 10, wherein data written to the secondary file system is able to be overwritten without involvement of the secondary file system.
A method for managing data storage in a computing system involves a primary file system and a secondary file system, where the secondary file system is used to store data that is a copy of data stored in the primary file system. The method includes writing data to the secondary file system, where the data is a copy of data stored in the primary file system. The secondary file system is configured to store data in a manner that allows the data to be overwritten without requiring the secondary file system to manage or control the overwrite operation. This means that the secondary file system does not need to perform any specific actions or checks when data is overwritten, allowing for more efficient and flexible data management. The method may also include synchronizing data between the primary and secondary file systems to ensure consistency. The secondary file system may be used for backup, redundancy, or other purposes where data integrity is important, but the ability to overwrite data without secondary file system involvement simplifies the process and reduces overhead. This approach is particularly useful in systems where performance and efficiency are critical, such as in high-speed data processing or storage systems.
17. The non-transitory computer-readable medium of claim 15, wherein the first file system is configured to overwrite portions of the block array that are used by the second file system, without involvement in the overwriting by the second file system.
A system and method for managing file systems in a computing environment where multiple file systems share a common storage resource. The problem addressed is the need to efficiently manage storage space when multiple file systems operate on the same block storage, particularly when one file system must overwrite data blocks that are also used by another file system. Traditional systems often require coordination between file systems to prevent data corruption or conflicts, which can introduce latency and complexity. The invention involves a first file system and a second file system that share a block array in a storage device. The first file system is configured to overwrite portions of the block array that are also used by the second file system, without requiring the second file system to participate in or be aware of the overwriting process. This allows the first file system to reclaim or modify storage blocks independently, improving efficiency and reducing the need for inter-file system coordination. The second file system continues to operate normally, accessing its allocated blocks as needed, while the first file system manages its own storage requirements without interference. The system ensures that the second file system's data integrity is maintained, even as the first file system performs overwrites on shared blocks. This approach is particularly useful in virtualized or containerized environments where multiple file systems may dynamically share storage resources.
19. The non-transitory computer-readable medium of claim 15, wherein the first file system is configured to provide consistency, and wherein the second file system is not configured to provide consistency.
A distributed storage system manages data across multiple file systems with differing consistency guarantees. The system includes a first file system that enforces strict consistency, ensuring that all clients see the same data state at any given time, and a second file system that does not enforce strict consistency, allowing for eventual consistency where updates may take time to propagate. The system dynamically routes data access requests to the appropriate file system based on the required consistency level, optimizing performance for applications that do not need immediate consistency. The first file system may use mechanisms like distributed locks or quorum-based protocols to maintain consistency, while the second file system may rely on asynchronous replication or relaxed consistency models. The system also includes a metadata service that tracks file system assignments and consistency requirements, enabling efficient routing of requests. This approach allows the system to balance performance and consistency, catering to different application needs within a single storage infrastructure. The system may also include mechanisms to migrate data between file systems based on changing consistency requirements or performance constraints.
20. The non-transitory computer-readable medium of claim 19, wherein data written to the second file system is able to be overwritten without involvement of the second file system.
A system and method for managing file systems in a computing environment addresses the challenge of efficiently handling data storage and retrieval while minimizing system overhead. The invention involves a primary file system and a secondary file system, where the secondary file system is designed to store data in a manner that allows for direct overwriting of data without requiring the secondary file system's involvement. This approach reduces latency and improves performance by bypassing the secondary file system's typical overhead when modifying stored data. The primary file system manages the overall data structure and coordinates with the secondary file system to ensure data integrity and consistency. The secondary file system is optimized for high-speed data access and modification, particularly in scenarios where frequent overwrites are necessary, such as in real-time data processing or high-performance computing applications. The system ensures that data written to the secondary file system can be directly overwritten without the need for the secondary file system to process the overwrite operation, thereby enhancing efficiency and reducing computational load. This method is particularly useful in environments where rapid data updates are critical, such as in financial transactions, scientific simulations, or large-scale data analytics.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
October 21, 2021
April 2, 2024
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.