fs: Polling backend support by probably-neb · Pull Request #54481 · zed-industries/zed

probably-neb · 2026-04-22T08:13:10Z

Self-Review Checklist:

I've reviewed my own diff for quality, security, and reliability
Unsafe blocks (if any) have justifying comments
The content is consistent with the UI/UX checklist
Tests cover the new/changed behavior
Performance impact has been considered and is acceptable

Closes #51340
Release Notes:

Linux/WSL: Added polling filesystem watching support in order to support file watching on file systems that do emit events through inotify, for example /mnt/c in WSL, network filesystems, and FUSE mounts. Polling should be automatically chosen over inotify when necessary, however it can be manually chosen by setting the ZED_FILE_WATCHER_MODE=poll env var

Auto-detect filesystems where inotify silently fails to deliver events (9P/drvfs on WSL2, NFS, CIFS/SMB, FUSE/sshfs) and use notify's PollWatcher instead of the native INotifyWatcher. Detection uses libc::statfs to check filesystem magic numbers, plus a WSL drvfs path heuristic as fallback. Environment variable overrides: - ZED_FILE_WATCHER_MODE=poll|native|auto (default: auto) - ZED_FILE_WATCHER_POLL_MS=2000 (range: 500-30000) No trait changes, no settings changes — pure auto-detection with env var escape hatches. Settings UI can be added in a follow-up. Ref: #51340, #38109

cla-bot · 2026-04-22T08:13:13Z

We require contributors to sign our Contributor License Agreement, and we don't have @lilith on file. You can sign our CLA at https://zed.dev/cla. Once you've signed, post a comment here that says '@cla-bot check'.

cla-bot · 2026-04-22T08:13:27Z

We require contributors to sign our Contributor License Agreement, and we don't have @lilith on file. You can sign our CLA at https://zed.dev/cla. Once you've signed, post a comment here that says '@cla-bot check'.

probably-neb · 2026-04-22T08:20:06Z

Hey @lilith, I took the time to create a PR on your Polling backend fork.
I ended up reworking it a bit to fit cleanly in with the existing architecture, primarily to re-use the existing watcher deduping logic which I think will be extra important to have for the polling backend.
If you have time to check this out and play around with it to make sure I didn't break anything on your end I'd appreciate it.
I included your commit so that you get credit for your work, but you'll need to sign the CLA in order for me to merge the commit. If you don't want to sign the CLA or for me to use your work, just lmk and I can rewrite the portions I've kept untouched (primarily the detection of when to use the poll backend)

cla-bot · 2026-04-22T11:55:25Z

We require contributors to sign our Contributor License Agreement, and we don't have @lilith on file. You can sign our CLA at https://zed.dev/cla. Once you've signed, post a comment here that says '@cla-bot check'.

lilith · 2026-04-22T21:13:50Z

When I click agree to the terms, it redirects me to the zed.dev home page.

…

On Wed, Apr 22, 2026, 5:55 AM cla-bot[bot] ***@***.***> wrote: *cla-bot[bot]* left a comment (zed-industries/zed#54481) <#54481?email_source=notifications&email_token=AAA2LHYDL56XRYJ2H2TPUAT4XCXMJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMRZGU4TKNJRGI32M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJNLQOJPWG33NNVSW45C7N5YGK3S7MNWGSY3L#issuecomment-4295955127> We require contributors to sign our Contributor License Agreement, and we don't have @lilith <https://github.com/lilith> on file. You can sign our CLA at https://zed.dev/cla. Once you've signed, post a comment here that says ***@***.*** <https://github.com/cla-bot> check'. — Reply to this email directly, view it on GitHub <#54481?email_source=notifications&email_token=AAA2LHYDL56XRYJ2H2TPUAT4XCXMJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMRZGU4TKNJRGI32M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJNLQOJPWG33NNVSW45C7N5YGK3S7MNWGSY3L#issuecomment-4295955127>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA2LH4KN55MOLSZE2KIBTL4XCXMJAVCNFSM6AAAAACYB7ZAOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEOJVHE2TKMJSG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

probably-neb · 2026-04-23T08:37:22Z

@cla-bot check

cla-bot · 2026-04-23T08:37:27Z

The cla-bot has been summoned, and re-checked this pull request!

Co-authored-by: Ben Kunkle <ben@zed.dev>

kubkon

Looks great!

auwi-nordic · 2026-04-27T08:18:29Z

Nice to see, just some notes for future improvements

Why not make the watcher mode and poll interval a real setting? Using environment variable is clunky
Ideally those settings should possible to override on a per-project level

Just for posterity I'd like to note that this change doesn't fully solve the issue of fs watching, and doesn't eliminate the need for manual refresh option as discussed here: #54150

…g callback handlers (#55683) (cherry-pick to preview) (#55941) Cherry-pick of #55683 to preview ---- In #54481, the `handle_event` function was altered to check for an `Access` event after the callbacks were acquired via a global state lock. The lock/Vec-collect has enough overhead (or maybe there's enough lock contention?) that the handler isn't performant enough to keep up with the volume of inotify events, and its queue fills up, resulting in [a rescan event getting emitted](https://github.com/notify-rs/notify/blob/79007aefb41d9f853d00656eb768600e3ea41ee0/notify/src/inotify.rs#L304-L306), which presumably results in *more* access events for the file as it's rescanned, which further serve to fill up the inotify queue. Moving the check for an `Access` event and returning before doing anything remotely expensive seems to resolve the issues I've been having lately. Not sure if it addresses the original issue in #53480 though. Longer-term, it might be prudent to do the event handler's heavy-lifting in a separate thread with its own event queue, and let the handler passed to the `notify` crate be just a dumb `tx` sender. Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [ ] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Related to #53480 Fixes #55829 Release Notes: - Fixed inotify event queue overflows on linux Co-authored-by: Josh Robson Chase <josh@robsonchase.com>

…g callback handlers (#55683) (cherry-pick to stable) (#55942) Cherry-pick of #55683 to stable ---- In #54481, the `handle_event` function was altered to check for an `Access` event after the callbacks were acquired via a global state lock. The lock/Vec-collect has enough overhead (or maybe there's enough lock contention?) that the handler isn't performant enough to keep up with the volume of inotify events, and its queue fills up, resulting in [a rescan event getting emitted](https://github.com/notify-rs/notify/blob/79007aefb41d9f853d00656eb768600e3ea41ee0/notify/src/inotify.rs#L304-L306), which presumably results in *more* access events for the file as it's rescanned, which further serve to fill up the inotify queue. Moving the check for an `Access` event and returning before doing anything remotely expensive seems to resolve the issues I've been having lately. Not sure if it addresses the original issue in #53480 though. Longer-term, it might be prudent to do the event handler's heavy-lifting in a separate thread with its own event queue, and let the handler passed to the `notify` crate be just a dumb `tx` sender. Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [ ] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Related to #53480 Fixes #55829 Release Notes: - Fixed inotify event queue overflows on linux Co-authored-by: Josh Robson Chase <josh@robsonchase.com>

…g callback handlers (zed-industries#55683) In zed-industries#54481, the `handle_event` function was altered to check for an `Access` event after the callbacks were acquired via a global state lock. The lock/Vec-collect has enough overhead (or maybe there's enough lock contention?) that the handler isn't performant enough to keep up with the volume of inotify events, and its queue fills up, resulting in [a rescan event getting emitted](https://github.com/notify-rs/notify/blob/79007aefb41d9f853d00656eb768600e3ea41ee0/notify/src/inotify.rs#L304-L306), which presumably results in *more* access events for the file as it's rescanned, which further serve to fill up the inotify queue. Moving the check for an `Access` event and returning before doing anything remotely expensive seems to resolve the issues I've been having lately. Not sure if it addresses the original issue in zed-industries#53480 though. Longer-term, it might be prudent to do the event handler's heavy-lifting in a separate thread with its own event queue, and let the handler passed to the `notify` crate be just a dumb `tx` sender. Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [ ] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Related to zed-industries#53480 Fixes zed-industries#55829 Release Notes: - Fixed inotify event queue overflows on linux

…s#56165) Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [x] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Closes zed-industries#56064 This behavior regressed in zed-industries#54481 Release Notes: - Fixed an issue where broken symlinks, permission errors, or other fs errors in watched directories could cause excessive CPU usage

…ry-pick to preview) (#56174) Cherry-pick of #56165 to preview ---- Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [x] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Closes #56064 This behavior regressed in #54481 Release Notes: - Fixed an issue where broken symlinks, permission errors, or other fs errors in watched directories could cause excessive CPU usage Co-authored-by: Ben Kunkle <ben@zed.dev>

…ry-pick to stable) (#56175) Cherry-pick of #56165 to stable ---- Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [x] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Closes #56064 This behavior regressed in #54481 Release Notes: - Fixed an issue where broken symlinks, permission errors, or other fs errors in watched directories could cause excessive CPU usage Co-authored-by: Ben Kunkle <ben@zed.dev>

Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [ ] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Closes zed-industries#51340 Release Notes: - Linux/WSL: Added polling filesystem watching support in order to support file watching on file systems that do emit events through `inotify`, for example `/mnt/c` in WSL, network filesystems, and FUSE mounts. Polling should be automatically chosen over `inotify` when necessary, however it can be manually chosen by setting the `ZED_FILE_WATCHER_MODE=poll` env var --------- Co-authored-by: Lilith River <lilith@imazen.io> Co-authored-by: Jakub Konka <kubkon@jakubkonka.com>

…s#56165) (cherry-pick to stable) (zed-industries#56175) Cherry-pick of zed-industries#56165 to stable ---- Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [x] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Closes zed-industries#56064 This behavior regressed in zed-industries#54481 Release Notes: - Fixed an issue where broken symlinks, permission errors, or other fs errors in watched directories could cause excessive CPU usage Co-authored-by: Ben Kunkle <ben@zed.dev>

…g callback handlers (zed-industries#55683) In zed-industries#54481, the `handle_event` function was altered to check for an `Access` event after the callbacks were acquired via a global state lock. The lock/Vec-collect has enough overhead (or maybe there's enough lock contention?) that the handler isn't performant enough to keep up with the volume of inotify events, and its queue fills up, resulting in [a rescan event getting emitted](https://github.com/notify-rs/notify/blob/79007aefb41d9f853d00656eb768600e3ea41ee0/notify/src/inotify.rs#L304-L306), which presumably results in *more* access events for the file as it's rescanned, which further serve to fill up the inotify queue. Moving the check for an `Access` event and returning before doing anything remotely expensive seems to resolve the issues I've been having lately. Not sure if it addresses the original issue in zed-industries#53480 though. Longer-term, it might be prudent to do the event handler's heavy-lifting in a separate thread with its own event queue, and let the handler passed to the `notify` crate be just a dumb `tx` sender. Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [ ] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Related to zed-industries#53480 Fixes zed-industries#55829 Release Notes: - Fixed inotify event queue overflows on linux

Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [x] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Closes zed-industries/zed#56064 This behavior regressed in zed-industries/zed#54481 Release Notes: - Fixed an issue where broken symlinks, permission errors, or other fs errors in watched directories could cause excessive CPU usage

Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [ ] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Closes zed-industries#51340 Release Notes: - Linux/WSL: Added polling filesystem watching support in order to support file watching on file systems that do emit events through `inotify`, for example `/mnt/c` in WSL, network filesystems, and FUSE mounts. Polling should be automatically chosen over `inotify` when necessary, however it can be manually chosen by setting the `ZED_FILE_WATCHER_MODE=poll` env var --------- Co-authored-by: Lilith River <lilith@imazen.io> Co-authored-by: Jakub Konka <kubkon@jakubkonka.com>

…g callback handlers (zed-industries#55683) In zed-industries#54481, the `handle_event` function was altered to check for an `Access` event after the callbacks were acquired via a global state lock. The lock/Vec-collect has enough overhead (or maybe there's enough lock contention?) that the handler isn't performant enough to keep up with the volume of inotify events, and its queue fills up, resulting in [a rescan event getting emitted](https://github.com/notify-rs/notify/blob/79007aefb41d9f853d00656eb768600e3ea41ee0/notify/src/inotify.rs#L304-L306), which presumably results in *more* access events for the file as it's rescanned, which further serve to fill up the inotify queue. Moving the check for an `Access` event and returning before doing anything remotely expensive seems to resolve the issues I've been having lately. Not sure if it addresses the original issue in zed-industries#53480 though. Longer-term, it might be prudent to do the event handler's heavy-lifting in a separate thread with its own event queue, and let the handler passed to the `notify` crate be just a dumb `tx` sender. Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [ ] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Related to zed-industries#53480 Fixes zed-industries#55829 Release Notes: - Fixed inotify event queue overflows on linux

…s#56165) Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [x] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Closes zed-industries#56064 This behavior regressed in zed-industries#54481 Release Notes: - Fixed an issue where broken symlinks, permission errors, or other fs errors in watched directories could cause excessive CPU usage

Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [ ] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Closes zed-industries#51340 Release Notes: - Linux/WSL: Added polling filesystem watching support in order to support file watching on file systems that do emit events through `inotify`, for example `/mnt/c` in WSL, network filesystems, and FUSE mounts. Polling should be automatically chosen over `inotify` when necessary, however it can be manually chosen by setting the `ZED_FILE_WATCHER_MODE=poll` env var --------- Co-authored-by: Lilith River <lilith@imazen.io> Co-authored-by: Jakub Konka <kubkon@jakubkonka.com>

…g callback handlers (zed-industries#55683) In zed-industries#54481, the `handle_event` function was altered to check for an `Access` event after the callbacks were acquired via a global state lock. The lock/Vec-collect has enough overhead (or maybe there's enough lock contention?) that the handler isn't performant enough to keep up with the volume of inotify events, and its queue fills up, resulting in [a rescan event getting emitted](https://github.com/notify-rs/notify/blob/79007aefb41d9f853d00656eb768600e3ea41ee0/notify/src/inotify.rs#L304-L306), which presumably results in *more* access events for the file as it's rescanned, which further serve to fill up the inotify queue. Moving the check for an `Access` event and returning before doing anything remotely expensive seems to resolve the issues I've been having lately. Not sure if it addresses the original issue in zed-industries#53480 though. Longer-term, it might be prudent to do the event handler's heavy-lifting in a separate thread with its own event queue, and let the handler passed to the `notify` crate be just a dumb `tx` sender. Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [ ] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Related to zed-industries#53480 Fixes zed-industries#55829 Release Notes: - Fixed inotify event queue overflows on linux

lilith and others added 5 commits April 20, 2026 16:14

shared helpers

51a18c6

collapse

052febb

restore

85e001b

simplify

7bb3a8d

probably-neb force-pushed the feat-fs-poll-watching branch from 56ed011 to 7bb3a8d Compare April 22, 2026 08:13

zed-community-bot Bot added the staff Pull requests authored by a current member of Zed staff label Apr 22, 2026

probably-neb mentioned this pull request Apr 22, 2026

Add PollWatcher fallback for WSL, network filesystems, and FUSE mounts #51340

Closed

clean

6a27fcd

cla-bot Bot added the cla-signed The user has signed the Contributor License Agreement label Apr 23, 2026

probably-neb marked this pull request as ready for review April 23, 2026 08:53

probably-neb assigned kubkon Apr 23, 2026

Add some telemetry

b2b321e

Co-authored-by: Ben Kunkle <ben@zed.dev>

kubkon approved these changes Apr 23, 2026

View reviewed changes

kubkon added this pull request to the merge queue Apr 23, 2026

Merged via the queue into main with commit aeb602d Apr 23, 2026
31 checks passed

kubkon deleted the feat-fs-poll-watching branch April 23, 2026 11:43

jrobsonchase mentioned this pull request May 4, 2026

fs: Pre-filter the event kind before acquiring global lock and cloning callback handlers #55683

Merged

5 tasks

probably-neb mentioned this pull request May 8, 2026

fs: Don't treat watcher errors as reason to do rescans #56165

Merged

5 tasks

Tenkir mentioned this pull request May 8, 2026

Polling Backend Hangs on Orbstack containers #56170

Closed

This was referenced May 8, 2026

fs: Don't treat watcher errors as reason to do rescans (#56165) (cherry-pick to preview) #56174

Merged

fs: Don't treat watcher errors as reason to do rescans (#56165) (cherry-pick to stable) #56175

Merged

github-actions Bot mentioned this pull request May 8, 2026

Review upstream Zed v1.1.6 neozed-industries/neo-zed#18

Closed

dbldippy mentioned this pull request May 8, 2026

Zed out of sync with changes made outside of editor #38109

Closed

karimknaebel mentioned this pull request May 10, 2026

Limit recursive poll file watching #56345

Closed

karimknaebel mentioned this pull request May 14, 2026

Remote SSH file explorer does not refresh for large projects #56156

Open

mattrobenolt mentioned this pull request May 19, 2026

OrbStack virtiofs should use native inotify instead of poll watcher #57103

Closed

yeskunall mentioned this pull request Jun 4, 2026

NFS directory with millions of files blocks all file opens #58583

Open

Navigation Menu

Uh oh!

Uh oh!

fs: Polling backend support - #54481

fs: Polling backend support#54481
kubkon merged 7 commits into
mainfrom
feat-fs-poll-watching

probably-neb commented Apr 22, 2026 •

edited

Loading

Uh oh!

cla-bot Bot commented Apr 22, 2026

Uh oh!

cla-bot Bot commented Apr 22, 2026

Uh oh!

probably-neb commented Apr 22, 2026

Uh oh!

cla-bot Bot commented Apr 22, 2026

Uh oh!

lilith commented Apr 22, 2026 via email

Uh oh!

probably-neb commented Apr 23, 2026

Uh oh!

cla-bot Bot commented Apr 23, 2026

Uh oh!

kubkon left a comment

Uh oh!

Uh oh!

auwi-nordic commented Apr 27, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Uh oh!

Conversation

probably-neb commented Apr 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cla-bot Bot commented Apr 22, 2026

Uh oh!

cla-bot Bot commented Apr 22, 2026

Uh oh!

probably-neb commented Apr 22, 2026

Uh oh!

cla-bot Bot commented Apr 22, 2026

Uh oh!

lilith commented Apr 22, 2026 via email

Uh oh!

probably-neb commented Apr 23, 2026

Uh oh!

cla-bot Bot commented Apr 23, 2026

Uh oh!

kubkon left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

auwi-nordic commented Apr 27, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

probably-neb commented Apr 22, 2026 •

edited

Loading