Notes on Using SeaweedFS

You should download the large_disk version.

Run ./weed version, if you see “Seaweed 8000GB”, then you are using the large disk version. If you see “Seaweed 30GB”, you are using the regular version.

For simplicity all commands are run under the root user.

Start a master node on Aloha

nohup ./weed master -mdir=”weed-idx” -ip= > master.out 2>&1 &

Check the log, you should see “Start Seaweed Master 8000GB” which again verifies you are using the large disk version.

Go to, this webpage should be up.

: Web page of master node

Start a volume node on la

The volume in SeaweedFS terminology doesn’t refer to the volume as in hard disk. The SeaweedFS volume is just a container of files and directories.

nohup ./weed volume -max=0 -mserver=”aloha:9333″ -dir=”/data/brick1/sw” > volume.out 2>&1 &

$ df -h /data/brick1
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda3       1.8T   77M  1.7T   1% /data/brick1

Refresh, Max under Cluster status becomes 59 from 0. 59*30=1770 GB, which matches the size of /dev/sda3.

The Topology section will show Click the link and you will see the actual file distribution on that volume node.

: Web page of volume node

Volume 1, 2, and 4 has files, while the others are empty for now. (If this is the first time you ever use Seaweedfs, all volumes should be empty for you.)


Up to now, the SeaweedFS storage is ready to use. Let’s create a file and test it.

echo ‘hello seaweedfs’ >

$ curl http://aloha:9333/dir/assign
$ curl -F,081bb85359

Go to, Volume 6 should contain 1 file (if it was 0).

You may argue this way to upload file is inconvenient, and I agree. Next section starts the filer service and provides a POSIX (FUSE) access point.

Start a filer node on aloha


nohup ./weed filer -master= > filer.out 2>&1 &

8888 appeared below is the default communication port of filer.


$ cp
$ curl -F "" "http://aloha:8888/path/to/sources/"
$ curl "http://localhost:8888/path/to/sources/"
hello seaweedfs

We can see the benefit of running the filer service is that we are able to access files using paths instead of the esoteric ids like 6,081bb85359.

The next step is to mount the SeaweedFS storage to our file system.

Run FUSE Mount on aloha

First check the mount point. I’m going to mount SeaweedFS storage to /home/shared-la.

$ ll /home/shared-la
ls: cannot access '/home/shared-la': Transport endpoint is not connected
$ df -h
df: /home/shared-la: Transport endpoint is not connected

It turns out my mount point is not “clean”, so I will run sudo umount /home/shared-la.

ll /home/shared-la
total 0

nohup ./weed mount -filer= -dir=/home/shared-la -filer.path=/ > mount.out 2>&1 &


ll -R /home/shared-la
total 0
drwxrwx--x 1 root root 0 2022-05-27 11:16 path

total 0
drwxrwx--x 1 root root 0 2022-05-27 11:16 to

total 0
drwxrwx--x 1 root root 0 2022-05-27 11:16 sources

total 1.5K
-rw-rw---- 1 root root 839 2022-05-27 11:16 nfs.out
-rw-rw---- 1 root root  16 2022-05-27 13:39

The uploaded through filer service shows up here, but the uploaded through the native API doesn’t.

$ cat
cat: Input/output error
$ sudo chown $(whoami):
$ cat
hello seaweedfs

Files uploaded through the filer API has owner and groups as root. The permissions and groups are enforced by FUSE. You can chown.

df -h /home/shared-la reports the total storage size is around 210GB. Figure says there are only 7 volumes on the volume node and each each volume holds up to 30GB despite of the large disk version, hence the total size 210GB. After you filled up the 210GB, Seaweedfs will generate another 7 volumes. You may pre-generate all volumes at once.

Add New Volume Node on Eureka

nohup ./weed volume -max=0 -mserver=”aloha:9333″ -dir=”/data/brick1/sw” > volume.out 2>&1 &



:wink: :twisted: :roll: :oops: :mrgreen: :lol: :idea: :evil: :cry: :arrow: :?: :-| :-x :-o :-P :-D :-? :) :( :!: 8-O 8)