Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Operations performed on sshfs mount no longer reloads #1731

Closed
Limero opened this issue May 26, 2024 · 2 comments
Closed

Operations performed on sshfs mount no longer reloads #1731

Limero opened this issue May 26, 2024 · 2 comments

Comments

@Limero
Copy link
Contributor

Limero commented May 26, 2024

I've been using sshfs mounted directories for a long time and it's been working fine, but recently any operations (creating/renaming/moving/deleting) performed on files/directories on the mount in lf will not update automatically (ctrl+r still works).

I'm not sure why it suddenly happens, but I can replicate it 100% of the times. I've tried rolling back from Fedora 40 to 38 and lf from r32 to r29 and it still happens, so it shouldn't be related to any recent changes in lf/sshfs.

The server I'm mounting is running Alpine Linux 3.20 (also happened before on 3.19) and the filesystem is ext4. It's possible that some update here caused it.

Map in lfrc I'm using to mount the directory:

map gn %mkdir -p /tmp/nuc && sshfs -o follow_symlinks -o workaround=renamexdev nuc: /tmp/nuc; lf -remote "send $id cd /tmp/nuc"

Possibly a duplicate of #582

@joelim-work
Copy link
Collaborator

I'm guessing it's a problem with mtime updating on sshfs/FUSE mounts.

The following code checks whether a directory should be reloaded or not:

lf/nav.go

Line 519 in aaf5bbb

case s.ModTime().After(dir.loadTime):

You can logging the variables and see what the values are.

@Limero
Copy link
Contributor Author

Limero commented May 27, 2024

@joelim-work I logged the modtime and noticed it always got set to 2016, ssh'ed in directly and noticed that the date was actually set to that. Turns out chrony (used for NTP timesync) stopped working for some reason, so I just changed over to using openntpd and everything works!

Thank you!

@Limero Limero closed this as completed May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants