Updates on NFS Server do not show up on Clients

[CBeerta]

What system are you running Yazi on?

Linux Wayland

What terminal are you running Yazi in?

foot 1.12.0

yazi --debug output

Yazi
    Version: 25.3.7 (570c6d3 2025-03-19)
    Debug  : false
    Triple : x86_64-unknown-linux-gnu (linux-x86_64)
    Rustc  : 1.85.1 (4eb16125 2025-03-15)

Ya
    Version: 25.3.7 (570c6d3 2025-03-19)

Emulator
    TERM                : Some("tmux-256color")
    TERM_PROGRAM        : Some("tmux")
    TERM_PROGRAM_VERSION: Some("3.5a")
    Brand.from_env      : Some(Foot)
    Emulator.detect     : Emulator { kind: Left(Foot), light: false, cell_size: Some((7, 17)) }

Adapter
    Adapter.matches    : Sixel
    Dimension.available: WindowSize { rows: 80, columns: 365, width: 2555, height: 1360 }

Desktop
    XDG_SESSION_TYPE           : Some("wayland")
    WAYLAND_DISPLAY            : Some("wayland-1")
    DISPLAY                    : Some(":0")
    SWAYSOCK                   : None
    HYPRLAND_INSTANCE_SIGNATURE: Some("882f7ad7d2bbfc7440d0ccaef93b1cdd78e8e3ff_1741547704_1836036775")
    WAYFIRE_SOCKET             : None

SSH
    shared.in_ssh_connection: false

WSL
    WSL: false

Variables
    SHELL           : Some("/usr/bin/bash")
    EDITOR          : Some("vim")
    VISUAL          : None
    YAZI_FILE_ONE   : None
    YAZI_CONFIG_HOME: None
    YAZI_ZOXIDE_OPTS: None
    FZF_DEFAULT_OPTS: Some("--bind ctrl-a:select-all,ctrl-d:deselect-all,ctrl-t:toggle-all --walker-skip .git,node_modules,target --walker=dir,follow --preview \'tree -C {}\'")

Text Opener
    default     : Some(Opener { run: "${EDITOR:=vi} \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true })
    block-create: Some(Opener { run: "${EDITOR:=vi} \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true })
    block-rename: Some(Opener { run: "${EDITOR:=vi} \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true })

Multiplexers
    TMUX               : true
    tmux version       : tmux 3.5a
    tmux build flags   : enable-sixel=Unknown
    ZELLIJ_SESSION_NAME: None
    Zellij version     : No such file or directory (os error 2)

Dependencies
    file          : 5.46
    ueberzugpp    : 2.9.6
    ffmpeg/ffprobe: 7.1 / 7.1
    pdftoppm      : 25.03.0
    magick        : 7.1.1-46
    fzf           : 0.60.3
    fd/fdfind     : 10.2.0 / No such file or directory (os error 2)
    rg            : 14.1.1
    chafa         : 1.14.5
    zoxide        : No such file or directory (os error 2)
    7zz/7z        : No such file or directory (os error 2) / 24.09
    jq            : 1.7.1

Clipboard
    wl-copy/paste: 2.2.1 / 2.2.1
    xclip        : 0.13
    xsel         : 1.2.1


See https://yazi-rs.github.io/docs/plugins/overview#debugging on how to enable logging or debug runtime errors.

Describe the bug

Hi,

I'm not sure if this is a Bug, or just a "NFS thing".

I have yazi open on a Client with a Directory that is mounted via NFS, and the directory Sorted by mtime.

If a File/Directory is updated on the same System, (just touch a file in another shell) the file/directory jumps to the top as expected.

If though i update a file on the Server, while having yazi open on the client nothing happens.

I've bound the refresh option key, but that does nothing either.

If i open another shell on the client, and check the timestamps with stat on the file i can see the updated timestamps on the client.

The NFS is mounted with:

eurybe.fritz.box:/data on /data type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=14,retrans=2,sec=sys,clientaddr=192.168.178.26,lookupcache=none,local_lock=none,addr=192.168.178.35,_netdev,x-systemd.automount,x-systemd.mount-timeout=10,x-systemd.idle-timeout=1min)

Both Client and Server are Linux based running Arch so client/server NFS Versions are identical.

Minimal reproducer

Have a NFS Client/Server

Open yazi on the client, sort directory by mtime, touch a file in that directory on the server

Anything else?

No response

Checklist

• I tried the latest nightly build, and the issue is still reproducible
• I updated the debug information (yazi --debug) input box to the nightly that I tried
• I can reproduce it after disabling all custom configs/plugins (mv ~/.config/yazi ~/.config/yazi-backup)

[github-actions]

Hey @CBeerta, I noticed that you did not correctly follow the issue template. Please ensure that:

• The bug can still be reproduced on the newest nightly build.
• The debug information (yazi --debug) is updated for the newest nightly.
• The non-optional items in the checklist are checked.

Issues with needs info will be marked ready once edited with the proper content, or closed after 2 days of inactivity.

[boydaihungst]

Same here. My temporary solution is open new tab, xD

[CBeerta]

Indeed, Opening a new Tab updates. It also Updates the view from which you opened the tab. So opening+closing "works".

But also, this isn't just a thing on NFS, i've been testing on the Server also, with the storage locally. If you have yazi open in a directory sorted by mtime, and a file in a subdirectory is created, the subdirectory in question doesn't move to the top as it should. Looking at the mtime with stat shows the directory inode got updated.