Userspace Filesystem Bind Mount for Hidden Data Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
When a userspace filesystem is mounted at a mountpoint of an existing filesystem, it hides underlying data, leading to data loss and accessibility issues, and upon unmounting and remounting, files may be written to the wrong filesystem, causing data to become hidden and difficult to recover without system downtime.
Innovation Solution
A system determines a mountpoint and creates a bind mount to access and incorporate hidden data from the underlying filesystem, allowing the userspace filesystem to manage data without copying it, ensuring data remains accessible and reducing downtime risks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a userspace filesystem is mounted at a mountpoint of an existing filesystem, then the userspace filesystem can be accessed and managed in userspace, but the underlying data becomes hidden and inaccessible
Solution Approach 1:
The patent implements a nested filesystem structure where the userspace filesystem is mounted within the context of the underlying filesystem. The bind mount mechanism allows the userspace filesystem to be nested at the mountpoint while maintaining a reference to the underlying data through the bind mount path, enabling both filesystems to coexist in a nested hierarchy where the userspace layer provides access controls and the underlying layer preserves data accessibility.
Solution Approach 2:
The bind mount path serves as an intermediary mechanism that bridges the userspace filesystem and the underlying filesystem. By creating a bind mount at a specific path that references the mountpoint, the system establishes an intermediate access route that allows applications to reach underlying data through the userspace filesystem interface without directly accessing the underlying filesystem, thus resolving the conflict between userspace management and data accessibility.
2Adaptability or versatility
If the userspace filesystem is unmounted, then the underlying filesystem is exposed, but data written to the mount path may be written to the wrong filesystem and become difficult to locate
Solution Approach 1:
The patent establishes the bind mount path and configuration before the userspace filesystem is mounted or unmounted. This preliminary setup ensures that the binding relationship between the mountpoint and the underlying data is pre-configured and persistent, so that regardless of the userspace filesystem's mounted state, the system knows where data should be written and can redirect writes appropriately, preventing data from being written to the wrong filesystem.
3Loss of information
If data is copied to recover hidden files, then data accessibility is restored, but system downtime is required
Solution Approach 1:
The bind mount mechanism maintains continuous access to underlying data throughout the userspace filesystem lifecycle. Instead of requiring data copying operations that would interrupt service, the bind mount path provides an ongoing, persistent reference to the underlying data that remains valid whether the userspace filesystem is mounted or unmounted. This allows data accessibility to be maintained continuously without requiring system downtime or data replication operations.
Data Source
AI summary
In some examples, a system may determine a mountpoint included in a first filesystem for mounting a userspace filesystem. For instance, the userspace filesystem may be executable in a userspace provided by an operating system. The system may determine a bind mount path for a mount path corresponding to the mountpoint. The system may bind mount, to the determined bind mount path, at least a portion of a second filesystem associated with the mount path corresponding to the mountpoint. In addition, the system may mount the userspace filesystem at the mountpoint, and may incorporate data from the second filesystem into the userspace filesystem through the bind mount path.