Overview
Updated at：2025-11-03
Overview
BOS FS mounts remote BOS server to local file systems, providing functions similar to network file systems for accessing BOS files via system commands or POSIX-like APIs. This kind of operation is as convenient as the usage of local disk, but it is unsuitable for scenarios with high performance requirements in production environments. BOS FS is recommended only for services dependent on mount or file system semantics; otherwise, BOS CMD is recommended.
BOS FS is built on FUSE, making it dependent on an operating system that supports FUSE. It currently supports basic POSIX semantics but does not accommodate hard links, extended attributes, file ACLs, or file locks.
| Installation package | Name and download address | MD5 | Description |
|---|---|---|---|
| Source package | bosfs-1.0.0.13.4.tar.gz | d8049ed01c23ed850e6f67081c019b5a | Install the source package. If you need to customize some functions, you can modify them directly. |
| libfuse | fuse-2.9.4.tar.gz | ecb712b5ffc6dffd54f4a405c9b372d8 | Source package required for libfuse installation |
Usage restrictions
- BOS FS is unsuitable for production environments requiring high performance.
- Metadata-related requests (especially directory listing) may experience delays due to the need for remote access to the BOS server.
- The atomicity of rename-related requests cannot be guaranteed, potentially causing inconsistencies between local data and the BOS backend.
- File system semantics are not fully supported, with limited functionality for features like file permissions and hard links.
- File operations in bosfs are mapped to local disk storage, requiring sufficient local disk space to be available.
- When multiple clients access the same or different mount points, it is the user's responsibility to maintain data consistency, which may lead to inconsistencies across clients.
- A remount is necessary after a machine reboot.