Skip to content

Files uploaded to external storage not shown immediately in Webinterface in shared folders #23988

Description

@rgl1234

Hello
There seems to be a problem in NC20.01 and external storages. When I place new files on external storage, they are not shown in WebInterface as normal. I get this Problem after upgrading from 19.04 to NC20.01.

Activity

  1. added
    0. Needs triagePending check for reproducibility or if it fits our roadmap
    on Nov 9, 2020
  2. mmaridev commented on Nov 9, 2020

    @mmaridev

    Can confirm, this issue was firstly reported by me and my team for Nextcloud 18. I just tried again and can confirm is still reproducible.

    Steps to reproduce:

    1. Add an external storage in Nextcloud
    2. Create a directory from Nextcloud and check via shell/SMB/NFS/whatever your storage: the directory has been created
    3. Via another protocol (NOT Nextcloud) create a file in the directory: the file won't show in the GUI

    Current workaround:
    Periodically run

    DELETE FROM ncfilecache WHERE storage NOT IN (SELECT f.numeric_id FROM ncstorages f);
    VACUUM FULL ncstorages;
    VACUUM FULL ncfilecache;
    DELETE FROM ncstorages;
    

    in your db

  3. rgl1234 commented on Nov 20, 2020

    @rgl1234
    Author

    problem still present in NC 20.02
    problem not present in NC 19.04

  4. ChewingBever commented on Jan 8, 2021

    @ChewingBever

    Can confirm this problem is still present in NC 20.04

  5. rgl1234 commented on Jan 18, 2021

    @rgl1234
    Author

    unfortunately still present in NC 20.05

    does someone have an idea what changed here from V19 to V20? It workes correctly in V19.....

  6. rgl1234 commented on Jan 23, 2021

    @rgl1234
    Author

    I could now find maybe the source of the problem. In external storages there is the checkbox
    "check for changes" > "once every direct access"
    In NC20, this functionality is only working, when the NC-user has direct access to the NC-Folder. But when the NC-user has access to the folder by "shared-folder", the "check for changes"-function is not executed and the user cannot see the correct content of the folder....

    Can someone confirm this bug in NC20?

  7. quizilkend commented on Jan 23, 2021

    @quizilkend

    I could now find maybe the source of the problem. In external storages there is the checkbox
    "check for changes" > "once every direct access"
    In NC20, this functionality is only working, when the NC-user has direct access to the NC-Folder. But when the NC-user has access to the folder by "shared-folder", the "check for changes"-function is not executed and the user cannot see the correct content of the folder....

    Can someone confirm this bug in NC20?

    Thanks for writing this up. I experience exactly the same on NC20.0.5

  8. ikarlo commented on Jan 23, 2021

    @ikarlo

    Thanks for writing this up. I experience exactly the same on NC20.0.5

    +1

  9. rgl1234 commented on Jan 30, 2021

    @rgl1234
    Author

    Does someone know how to proceed with this bug to have it fixed in next release?

  10. adrfantini commented on Feb 16, 2021

    @adrfantini

    Just here to confirm this behaviour in the latest version from the official docker, using local storage. Can reproduce 100% of the time.

  11. Flunkyball commented on Mar 24, 2021

    @Flunkyball

    +1
    NC 20.0.2

  12. rgl1234 commented on Mar 25, 2021

    @rgl1234
    Author

    thanks @addagrm for your feedback. So I hope someone from nextcloud will have a look into this problem soon...

  13. Flunkyball commented on Mar 25, 2021

    @Flunkyball

    @addagrm
    Is the refresh working if the external storage is not shared ? My users have their home directory included as external storage via SFTP (tried SMB as well) and experience the same issue - no refresh what so ever.

  14. 29 remaining items

  15. ib-mlatin commented on Aug 25, 2021

    @ib-mlatin

    I'm having this same issue as well. All our users are set up with "User entered" credentials to preserve file system permissions. I have yet to put the files:scan command to the test, but so far the only way I have been able to get the client to match the web-ui is to access the folder in the web-ui first, and then it will be up to date on the client.

    Since most of the users have the same external storage, is it possible to just run the files:scan command for a single user and have the updates propagate to the rest of them, or is external storage coded in Nextcloud where each user has their own set of file IDs for external storage?

  16. szaimen commented on Aug 25, 2021

    @szaimen
    Contributor

    Hi, see #28377 for a potential fix. Testing is as always welcome! :)

  17. ib-mlatin commented on Aug 30, 2021

    @ib-mlatin

    I'll see if I can spin up a duplicate(ish) install that I can test that on. I also answered this part myself. This might help someone resolve this temporarily.

    Since most of the users have the same external storage, is it possible to just run the files:scan command for a single user and have the updates propagate to the rest of them, or is external storage coded in Nextcloud where each user has their own set of file IDs for external storage?

    No it does not, you need to sync every user that has access to external storage. Definitely not ideal if you have a lot of users.

  18. rgl1234 commented on Sep 2, 2021

    @rgl1234
    Author

    thanks @szaimen
    I just tested the fix in NC21 and can confirm, that the problem seems to be solved.....

  19. added and removed
    1. to developAccepted and waiting to be taken care of
    on Sep 4, 2021
  20. mmaridev commented on Oct 29, 2021

    @mmaridev

    I tested in Nextcloud 22.2.0.2 and can confirm is now working.
    On my side two were the configurations that did the trick:

    1. setting ldapExpertUsernameAttr to uid (maybe because in the oc_storages_credentials table the user is saved with username?)
    2. set filesystem_check_changes: 1 in the external mount options. For some reason, this wasn't done before.

    Further references: https://gitlab.fuss.bz.it/fuss-team/fuss-nc/-/blob/master/nextcloud-fuss/configure-fuss.sh

  21. ciberboy commented on Oct 24, 2022

    @ciberboy

    2. filesystem_check_changes: 1

    Hi

    Where did you set this option? filesystem_check_changes: 1

  22. mmaridev commented on Oct 24, 2022

    @mmaridev

    @ciberboy

    Where did you set this option? filesystem_check_changes: 1

    via occ command, see this link.

  23. rgl1234 commented on May 30, 2023

    @rgl1234
    Author

    hello @szaimen
    Unfortunately, this bug is back again after having updated my DB from V25 to V26.0.1
    So I think another fix is needed for V26.0.1

  24. rgl1234 commented on Jun 15, 2023

    @rgl1234
    Author

    hello @szaimen
    Bug still available in V27.0.0

  25. szaimen commented on Jun 15, 2023

    @szaimen
    Contributor

    Hi, please open a new bug report then with up-to-date information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions