Shared drive over SMB regressing more and more over time

[groovybits]

Check for existing issues

• Completed

Describe the bug / provide steps to reproduce it

SMB share with the code used to work well. Lately it shows more issues of errors that are not true actual errors. Often gets slow and loses information, which is also increasing in occurrence as updates happen. Seems if I have too many files added to the directory it especially starts having issues, yet it happens just in normal operation now where I was able to go for days opened and never have issues.

Environment

Linux Samba SMB sharing to Mac OS

If applicable, add mockups / screenshots to help explain present your vision of the feature

No response

If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.

No response

[JosephTLyons]

@groovybits - can you share more about your Zed / SMB share setup? I'm not familiar with using Zed with this workflow.

[groovybits]

So basically it's just a samba SMB shared drive, basic setup built in to centos 7.9.

I get issues where I will save and it says the file changed on disk, but it should not have. If I force save, it corrupts. This was not happening as much a month ago or more.

It seems to often "flake out" and all the files disappear, yet I am on wired lan next to the file server smb system.

Yet it could be the system being sluggish, it feels like Zed doesn't handle this very well and starts making decisions that can lead to file corruption in this case.

[groovybits]

Also I get issues where Zed suddenly has all these "errors" about type's not existing that are basic / built in. Till I reopen Zed or close/repopen the project. It may stop formatting or the rust analyzer crashes. So that also seems to be happening sometimes now which is very new, did not do that a few weeks ago.

[groovybits]

More details, it seems to happen if I put any load on the fileserver. Zed thinks the files vanish over and over. Zed freaks out and starts trying to do things that corrupt the files if not very careful, asking to save them etc when they are not going to save "correctly" from Zed for some reason trying to save it as empty.

Traits somehow get forgotten and Zed starts to have errors for things that are not errors. Like Zed can't see all the files.

The files are accessible and generally fine, it's some sort of timeout/latency reaction of Zed when the files are latent and begins to do things that are destructive potentially. Seems to not just wait, and start thinking the file needs to be written I guess. This didn't happen a month ago + like this from what I can tell. It might be related to general file system slowness because if I start writing new files in the same directory as the project outside of Zed then Zed usually crashes.

[groovybits]

This is much worse suddenly. Indenting stops working for some reason on save, and save can take minutes to work. Every update degrades SMB access from my mac to a linux samba server. The server is right here local, fast, and should not be latent at all and is not from mac etc.

it feels like the file system is polled or something too much, and causes latency from Zed doing something aggressive on the smb share.

[groovybits]

This is much worse suddenly. Indenting stops working for some reason on save, and save can take minutes to work. Every update degrades SMB access from my mac to a linux samba server. The server is right here local, fast, and should not be latent at all and is not from mac etc.

it feels like the file system is polled or something too much, and causes latency from Zed doing something aggressive on the smb share.

This finally ended, back to more off/on issues with files acting funny with saving/appearing then vanishing for a moment.

So far I haven't seen issues accessing the file system other ways during these times.

[groovybits]

Now this fails to recognize when the file has already been saved, so it never thinks it saved it but it has saved on the file server. :( This is totally breaking it now, something changed recently in the last week to cause this. It never did this before, now it feels very dysfunctional and almost impossible to use / rely on using on an SMB filesystem :/

[smellord]

I also have massive smb problems on macOS .. sometimes it sees only the latest file I had opened, when I want to save it takes 15 seconds to make the blue dot disappear, most of the times it takes 10 seconds or more to open a file after I click on it. It's frustrating