NFS client directory doesn't match directory on mergerfs host #1183
Closed
hwwilliams
started this conversation in
General
Replies: 1 comment 9 replies
-
Are you changing things out of band to mergerfs or nfs? |
Beta Was this translation helpful? Give feedback.
9 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have noticed that certain directories on NFS clients connected to the mergerfs pool are accessing a directory that is not up to date with the mergerfs pool on the mergerfs host.
The mergerfs host is configured for NFS v4 only and the client is configured to mount the NFS share (mergerfs pool) using the following options: 10.0.0.10:/comics /mnt/mergerfs/comics nfs defaults,nfsvers=4,minorversion=2,proto=tcp,port=2049 0 0
I have attached a screenshot below of an NFS client on the top where a comic issue 001 is missing but the mergerfs host does have the issue 001 in the same directory.
I'm not doing any file caching but clearly something is being cached or not updated, does anyone have any suggestions?
OS: Debian 11
Mergerfs Version: 2.35.1
Mergerfs Mount Options: /mnt/mergerfs/data* /mnt/mergerfs/pool fuse.mergerfs branches-mount-timeout=300,cache.files=off,category.create=pfrd,dropcacheonclose=true,fsname=mergerfs,inodecalc=path-hash,lazy-umount-mountpoint=true,link_cow=true,noforget,readahead=2048,threads=16,xattr=nosys 0 0
Beta Was this translation helpful? Give feedback.
All reactions