Selfhosted

56953 readers

1844 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

NFS: stale file handle in contaniers after snapraid sync (lemmy.ml)

submitted 2 days ago* (last edited 2 days ago) by peregus@lemmy.ml to c/selfhosted@lemmy.world

10 comments fedilink hide all child comments

Hi all! I've moved Nextcloud and Immich data folders from local to a NFS folder. Everything is fine except when snapraid runs on the NFS server. Structure:

Proxmox host that also act as a NFS server
NFS exported folders are in a MergerFS folder (BRTFS) that are part of snapraid (2 data drives and 1 parity drives)
A Proxmox VM with all the Docker containers
Inside the VM I've mounted the NFS shares that are always available (even after the backup)

In the containers the folders are bind mounted like this /mnt/nfs/nextcloud/data:/var/www/html/data After the backup the NFS share are still available in the VM, but if I enter the container I get:

root@nextcloud-app:/var/www/html# ls -latr data
ls: cannot access 'data': Stale file handle

The NFS are mounted like this:

172.5.0.5:/mnt/pool/@nextcloud /mnt/nfs/nextcloud nfs vers=4,rw,hard,intr,timeo=600,retrans=10,_netdev,nofail,x-systemd.requires=network-online.target 0 0

How can I solve this problem?

you are viewing a single comment's thread
view the rest of the comments

[–] jaybone@lemmy.zip 1 points 2 days ago (1 children)

@remindme@mstdn.social 2 days

I don’t have a good answer but I’m super curious about this.

You say the mount is still fine from the VM, so it must be something with how the docker mounts are configured.

In the early days of docker there used to be a tool that used rsync to sync changes between host and container filesystems when such support wasn’t yet available on some systems (like Mac). I’m wondering if something similar is needed here. Or some additional options in your docker mount mappings.

[–] remindme@mstdn.social -1 points 2 days ago

@jaybone Ok, I will remind you on Tuesday Mar 17, 2026 at 12:02 PM UTC.