NFS example doesn't mount from linux VM

[jfmatth]

Hi, I'm very excited to get ZeroFS working, but NFS clients just don't seem to want to connect. Local NFS connections on the same server as zero work fine, but those same commands on a remote client do not.

[cache]
dir = "${HOME}/.cache/zerofs"
disk_size_gb = 10.0
memory_size_gb = 1.0

#[storage]
#url = "file:///tmp/zerofs-test"
#encryption_password = "password"

[storage]
url = "s3://zerofs/zerofs-data"
encryption_password = "password"

[aws]
access_key_id = "xxxx"
secret_access_key = "xxxxx"
region = ""              # Optional, defaults to us-east-1
endpoint = "https://s3.lax.sharktech.net/"  # Optional for S3-compatible services
allow_http = "false"                # Set to true for non-HTTPS endpoints
conditional_put = "redis://localhost:6379"  # For stores without conditional put

[servers.nfs]
addresses = ["0.0.0.0:2049"]

Trying to connect to ZeroFS server from another IP

jfmatth@rclone-nfs:~$ sudo mount -v -t nfs -o vers=3,async,nolock,tcp,port=2049,mountport=2049 192.168.100.50:/ /mnt/zerofs
mount.nfs: timeout set for Fri Apr 10 03:55:58 2026
mount.nfs: trying text-based options 'vers=3,nolock,tcp,port=2049,mountport=2049,addr=192.168.100.50'
mount.nfs: mount(2): Operation not permitted
mount.nfs: Operation not permitted for 192.168.100.50:/ on /mnt/zerofs
jfmatth@rclone-nfs:~$

Starting ZeroFS

root@vm-nfscache:~# zerofs run --config zerofs.toml
2026-04-10T03:55:30.471843Z  INFO zerofs::cli::server: Starting ZeroFS server with AmazonS3(zerofs) backend
2026-04-10T03:55:30.471867Z  INFO zerofs::cli::server: DB Path: zerofs-data
2026-04-10T03:55:30.471871Z  INFO zerofs::cli::server: Base Cache Directory: /root/.cache/zerofs
2026-04-10T03:55:30.471875Z  INFO zerofs::cli::server: Cache Size: 10 GB
2026-04-10T03:55:30.471886Z  INFO zerofs::cli::server: Checking bucket identity...
2026-04-10T03:55:30.510384Z  INFO zerofs::bucket_identity: Found existing bucket ID: c2cd6cbc-c2fb-4b9e-86de-6aaf63ffb61b
2026-04-10T03:55:30.510424Z  INFO zerofs::cli::server: Bucket ID: c2cd6cbc-c2fb-4b9e-86de-6aaf63ffb61b, Cache directory: /root/.cache/zerofs/bucket_c2cd6cbc
2026-04-10T03:55:30.517266Z  INFO zerofs::storage_compatibility: Checking storage provider compatibility (conditional writes for fencing)...
2026-04-10T03:55:30.569493Z  INFO zerofs::storage_compatibility: Storage provider compatibility check passed
2026-04-10T03:55:30.569560Z  INFO zerofs::cli::server: Loading or initializing encryption key from object store
2026-04-10T03:55:30.755158Z  INFO zerofs::cli::server: Cache allocation - Disk: 10.00GB, Memory: 1.00GB
2026-04-10T03:55:30.755201Z  INFO zerofs::cli::server: SlateDB in-memory block cache: 1000 MB
2026-04-10T03:55:30.755846Z  INFO zerofs::cli::server: Opening database in read-write mode
2026-04-10T03:55:30.756279Z  INFO slatedb::db::builder: opening SlateDB database [path=zerofs-data, settings={"flush_interval":"30s","wal_enabled":true,"manifest_poll_interval":"1s","manifest_update_timeout":"300s","min_filter_keys":1000,"filter_bits_per_key":10,"l0_sst_size_bytes":134217728,"l0_max_ssts":16,"max_unflushed_bytes":1000000000,"compactor_options":null,"compression_codec":null,"object_store_cache_options":{"root_folder":"/root/.cache/zerofs/bucket_c2cd6cbc","max_cache_size_bytes":10000000000,"part_size_bytes":4194304,"cache_puts":true,"preload_disk_cache_on_startup":null,"scan_interval":"3600s"},"garbage_collector_options":{"manifest_options":{"interval":"60s","min_age":"60s"},"wal_options":{"interval":"60s","min_age":"60s"},"compacted_options":{"interval":"60s","min_age":"60s"},"compactions_options":{"interval":"60s","min_age":"60s"}},"default_ttl":null}]
2026-04-10T03:55:31.034215Z  INFO zerofs::cli::server: Starting NFS server on 0.0.0.0:2049
2026-04-10T03:55:31.034332Z  INFO zerofs::webui: Web UI server listening on http://0.0.0.0:8080
2026-04-10T03:55:31.034696Z  INFO zerofs::fs::gc: Starting garbage collection task (runs continuously)
2026-04-10T03:55:31.036123Z  INFO zerofs::cli::server: Starting stats reporting task (reports to debug every 5 seconds)
2026-04-10T03:55:31.036156Z  INFO zerofs::cli::server: Starting periodic flush task (flushes every 30 seconds)

Any help is appreciated. Love this project, super easy and fast.

[Barre]

Hi,

Immediately after failing the mount command, can you run dmesg -T, and provide the tail of the output here?

Please provide cat /proc/self/status | grep CapEff as well.

[jfmatth]

@Barre Really appreciate the quick response.

Turns out, I was using a Proxmox LXC client and that may have been the issue :(.

I got the mount working directly from Proxmox, doing more testing now.

[Barre]

Turns out, I was using a Proxmox LXC client and that may have been the issue :(.

Indeed, that's the issue!

[jfmatth]

Thanks again for the quick response.

The "VM" you run in the browser is super cool, did you bring in another project for that or write your own. Slick.

[jfmatth]

@Barre Silly question, - all the examples about connecting to Zero from a client show using "/" as the folder to connect to, is it just a matter of making a folder on the filesystem and then connecting to "/folder" from the NFS client?

I ask since typically that might be another export for NFS, but seems like you already handle this.

Thanks again for this project, it's amazing

[Barre]

all the examples about connecting to Zero from a client show using "/" as the folder to connect to, is it just a matter of making a folder on the filesystem and then connecting to "/folder" from the NFS client?

It should work that way for NFS. 9p is different and doesn't handle aname, but this could be changed.

Thanks again for this project, it's amazing

Thank you!

[jfmatth]

Hi @Barre,

My adventure with ZeroFS continues.

For whatever reason, Proxmox proper won't connect to the NFS server, but the CLI of the Proxmox nodes do, odd.

I'm wondering if on the ZeroFS server I can re-share the NFS from ZeroFS to a Linux NFS server and have proxmox connect to that?

Thoughts?

Thanks again for this project, it's amazing.