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

Mounted FTP-Server shows files not correctly #10916

Closed
stefan-niedermann opened this issue Sep 7, 2014 · 8 comments
Closed

Mounted FTP-Server shows files not correctly #10916

stefan-niedermann opened this issue Sep 7, 2014 · 8 comments

Comments

@stefan-niedermann
Copy link

OC 7.0.2
Steps to reproduce:

  1. Set up OC
  2. Mount a FTP-Server into your OC instance
  3. Access the FTP-Server via FTP
  4. Create a test.txt-File on your FTP-Server via FTP
  5. Reload OC
    Current behaviour: OC did not recognize that FTP-Folder-Content changed and still shows me the message "All empty here - load up new files!"
    Expected behaviour: After Pressing F5, OC should show me the created test.txt file

Possible cause: Caching?

@PVince81
Copy link
Contributor

PVince81 commented Sep 8, 2014

No, problem is that the FTP stream wrapper doesn't provide the mtime of the folders, so update detection cannot work this way. Need to either switch to an alternative FTP implementation (ie rewrite) or find another way to detect updates.

Mentioned here #6395 (comment)

But let's keep this ticket here as it's more explicit.

@MTRichards
Copy link
Contributor

If I recall, there is a config file setting to update this behavior: on access, on first access, or never for a scan of the external storage system. Perhaps this is set to never?

oC 6 external storage, and FTP in particular, worked by scanning everything on access. So this is either a bug, or the config file needs to be set to on access.

@craigpg craigpg added this to the need more information milestone Sep 8, 2014
@stefan-niedermann
Copy link
Author

where exactly is the config file and which properties do i have to set? i would test this.

@MTRichards
Copy link
Contributor

I see this in the config.sample.php here:
/*

  • specifies how often the filesystem is checked for changes made outside owncloud
  • 0 -> never check the filesystem for outside changes, provides a performance increase when it's certain that no changes are made directly to the filesystem
  • 1 -> check each file or folder at most once per request, recomended for general use if outside changes might happen
  • 2 -> check every time the filesystem is used, causes a performance hit when using external storages, not recomended for regular use
    /
    'filesystem_check_changes' => 1,
    /
    If true, prevent owncloud from changing the cache due to changes in the filesystem for all storage */
    'filesystem_cache_readonly' => false,

@MTRichards
Copy link
Contributor

@stefan-niedermann
Copy link
Author

Since the default value seems to be 1, i don't think it's the problem. I do not override this value in my config.php.
I will tomorrow test, if it helps if i explicitly override the value with 1 or with 2. this would cause performance issues, but better bad performance than not working.
standby.

@mpeltier
Copy link

I have the same problem using 7.0.3 with filesystem_check_changes = 1 or 2. New file uploaded using an FTP client is not seen. If I run "php console.php files:scan --all", the file appears. As a workaround, I have set up a cron job in order to run this command periodically.

The cron doc says (http://doc.owncloud.org/server/7.0/admin_manual/configuration/background_jobs.html) "ownCloud plug-in applications register actions with cron.php automatically to take care of typical housekeeping operations, such as garbage collecting of temporary files or checking for newly updated files using filescan() for externally mounted file systems.". So is this supposed to work without additional external cron?

Thanks,
Mathieu

@MorrisJobke
Copy link
Contributor

Duplicate of #11797

@MorrisJobke MorrisJobke modified the milestone: need more information Jan 14, 2015
@lock lock bot locked as resolved and limited conversation to collaborators Aug 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants