Table of Contents
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
To mount SeaweedFS using /etc/fstab (such as on boot):
- Follow the directions in https://github.com/seaweedfs/seaweedfs/wiki/FUSE-Mount for setting up a SeaweedFS mount subtype for FUSE (hint:
cp weed /sbin/weed) - Install SeaweedFS as usual, making sure any specific settings (such as
security.toml) are in the correct location to be read - Add the fstab entry as described below
- But make sure that
systemd-fstab-generator(8)is not used on your system
If you have a single filer server, this is the syntax you will use:
fuse /path/to/mountpoint fuse.weed filer=localhost:8888,filer.path=/,defaults,_netdev 0 0
If you have multiple filer servers, this is the syntax you will use:
fuse /path/to/mountpoint fuse.weed filer='192.168.0.1:8888,192.168.0.2:8888',filer.path=/,defaults,_netdev 0 0
Place the appropriate line into /etc/fstab and attempt to mount your filesystem. If you encounter any issues, run weed mount directly in verbose/debug mode to diagnose the issue, and switch back to fstab-style mounting once you have resolved the issues.
Systemd
-
No matter what systemd options (
nofail,x-systemd.device-timeout,x-systemd.mount-timeout, etc.) you add to /etc/fstab, you won’t be able to makesystemd.mount(5)handle the mount properly. You will always get an error when starting mount unit, even though the filesystem ends up being mounted. -
x-systemd.automountdoesn’t work at all. -
The
_netdevresults in errors like:kernel: fuse: Unknown parameter '_netdev'p.s. Not sure if it’s related. (systemd 255.6)
In general, if your system is deeply integrated with systemd, it is better to create systemd.service(5) to mount.
Introduction
API
Configuration
- Replication
- Store file with a Time To Live
- Failover Master Server
- Erasure coding for warm storage
- Server Startup Setup
- Environment Variables
Filer
- Filer Setup
- Directories and Files
- Data Structure for Large Files
- Filer Data Encryption
- Filer Commands and Operations
- Filer JWT Use
Filer Stores
- Filer Cassandra Setup
- Filer Redis Setup
- Super Large Directories
- Path-Specific Filer Store
- Choosing a Filer Store
- Customize Filer Store
Advanced Filer Configurations
- Migrate to Filer Store
- Add New Filer Store
- Filer Store Replication
- Filer Active Active cross cluster continuous synchronization
- Filer as a Key-Large-Value Store
- Path Specific Configuration
- Filer Change Data Capture
FUSE Mount
WebDAV
Cloud Drive
- Cloud Drive Benefits
- Cloud Drive Architecture
- Configure Remote Storage
- Mount Remote Storage
- Cache Remote Storage
- Cloud Drive Quick Setup
- Gateway to Remote Object Storage
AWS S3 API
- Amazon S3 API
- AWS CLI with SeaweedFS
- s3cmd with SeaweedFS
- rclone with SeaweedFS
- restic with SeaweedFS
- nodejs with Seaweed S3
- S3 API Benchmark
- S3 API FAQ
- S3 Bucket Quota
- S3 API Audit log
- S3 Nginx Proxy
- Docker Compose for S3
AWS IAM
Machine Learning
HDFS
- Hadoop Compatible File System
- run Spark on SeaweedFS
- run HBase on SeaweedFS
- run Presto on SeaweedFS
- Hadoop Benchmark
- HDFS via S3 connector
Replication and Backup
- Async Replication to another Filer [Deprecated]
- Async Backup
- Async Filer Metadata Backup
- Async Replication to Cloud [Deprecated]
- Kubernetes Backups and Recovery with K8up
Metadata Change Events
Messaging
Use Cases
Operations
Advanced
- Large File Handling
- Optimization
- Volume Management
- Tiered Storage
- Cloud Tier
- Cloud Monitoring
- Load Command Line Options from a file
- SRV Service Discovery
- Volume Files Structure