GNOME Bugzilla – Bug 698731
nautilus needs manual refresh to show changes in cifs mounted folders
Last modified: 2021-06-18 15:54:06 UTC
If the nautilus window shows files from network folders mounted with cifs, changes in this files are mostly not shown until a manual refresh (F5). Most of the time, when I type "touch test" or "rm test" in the terminal the change in the file list is not shown until I refresh with F5. Changes from other users over the network are never shown without explicit refresh. It seems to be related with inotify, because most of the time "inotifywait -m /some-cifs-mounted-dir" does not show file events after "touch" or "rm" of files in this dir. Sometimes inotify does show the events and nautilus still does not show the changes. Usually, after a manual refresh in this dir, the subsequent events shown by inotify are than also shown in the nautilus window. File operations done by nautilus are always shown by inotifywait. System: Ubuntu 12.04, amd64 nautilus 3.4.2 inotify-tools 3.13
When you say "network folders mounted with cifs" do you refer to gvfs SMB mounts? For those, what you see is expected behavior: the gvfs backend for SMB doesn't support file monitoring. If you're mounting them directly with the kernel cifs driver on a local directory using e.g. fstab, then the bug must be somewhere else, because they will be treated as local files from Nautilus.
The folders are mounted with the cifs kernel driver. File changes generated by commands in a terminal window are shown by inotifywait and gvfs-monitor-dir. But theses changes are not shown in the nautilus window.
confirming this bug for cifs connections mounted by system via an entry in /etc/fstab and ALSO for smb connections (just mounted through "smb://" on the location bar).
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version of Files (nautilus), then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/nautilus/-/issues/ Thank you for your understanding and your help.