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

[Bug]: Wrong metadata due to inconsistent scanning behavior of external storage #35066

Closed
5 of 9 tasks
haarp opened this issue Nov 10, 2022 · 4 comments
Closed
5 of 9 tasks
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap 27-feedback bug feature: external storage feature: filesystem

Comments

@haarp
Copy link

haarp commented Nov 10, 2022

⚠️ This issue respects the following points: ⚠️

  • This is a bug, not a question or a configuration/webserver/proxy issue.
  • This issue is not already reported on Github (I've searched it).
  • Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
  • Nextcloud Server is running on 64bit capable CPU, PHP and OS.
  • I agree to follow Nextcloud's Code of Conduct.

Bug description

When an local external storage is freshly added, manually navigating it will update folders with the correct timestamp. But waiting for it to automatically get scanned will update folders with the wrong timestamp (time of scan) instead.

Steps to reproduce

  1. Add new local external storage w/ Check for changes=Once every direct access
  2. Navigate to folder in web interface
  3. -> Storage and all subfolders marked as pending
  4. Navigate one subfolder and all its items
  5. -> Subfolders are eventually updated properly with the correct timestamp ✓
  6. Wait for Nextcloud to scan the remaining subfolders on its own (cron?)
  7. -> Remaining subfolders have wrong timestamp, i.e. from time of scanning.

Expected behavior

Correct timestamp used in both cases

Installation method

Community Manual installation with Archive

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.1

Web server

Nginx

Database engine version

PostgreSQL

Is this bug present after an update or on a fresh install?

Updated to a major version (ex. 22.2.3 to 23.0.1)

Are you using the Nextcloud Server Encryption module?

No response

What user-backends are you using?

  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other

Configuration report

{
    "system": {
        "instanceid": "***REMOVED SENSITIVE VALUE***",
        "passwordsalt": "***REMOVED SENSITIVE VALUE***",
        "secret": "***REMOVED SENSITIVE VALUE***",
        "trusted_domains": [
            "***REMOVED SENSITIVE VALUE***",
            "***REMOVED SENSITIVE VALUE***"
        ],
        "datadirectory": "***REMOVED SENSITIVE VALUE***",
        "overwrite.cli.url": "***REMOVED SENSITIVE VALUE***",
        "overwritewebroot": "\/",
        "htaccess.RewriteBase": "\/",
        "version": "24.0.7.1",
        "knowledgebaseenabled": false,
        "apps_paths": [
            {
                "path": "\/var\/www\/nextcloud\/apps",
                "url": "\/apps",
                "writable": true
            }
        ],
        "dbtype": "pgsql",
        "dbname": "***REMOVED SENSITIVE VALUE***",
        "dbhost": "***REMOVED SENSITIVE VALUE***",
        "dbtableprefix": "oc_",
        "dbuser": "***REMOVED SENSITIVE VALUE***",
        "dbpassword": "***REMOVED SENSITIVE VALUE***",
        "default_phone_region": "DE",
        "installed": true,
        "loglevel": 2,
        "mail_smtpmode": "sendmail",
        "maintenance": false,
        "maintenance_window_start": 1,
        "memcache.local": "\\OC\\Memcache\\APCu",
        "memcache.distributed": "\\OC\\Memcache\\Redis",
        "memcache.locking": "\\OC\\Memcache\\Redis",
        "mail_from_address": "***REMOVED SENSITIVE VALUE***",
        "mail_domain": "***REMOVED SENSITIVE VALUE***",
        "updater.release.channel": "stable",
        "preview_max_x": 2048,
        "preview_max_y": 2048,
        "preview_max_filesize_image": 100,
        "preview_max_memory": 256,
        "app_install_overwrite": [
            "checksum",
            "files_3d"
        ],
        "redis": {
            "host": "***REMOVED SENSITIVE VALUE***",
            "port": 0,
            "password": "***REMOVED SENSITIVE VALUE***",
            "dbindex": 0
        }
    }
}

List of activated Apps

Enabled:
  - accessibility: 1.10.0
  - activity: 2.16.0
  - calendar: 3.5.2
  - camerarawpreviews: 0.8.0
  - checksum: 1.1.5
  - cloud_federation_api: 1.7.0
  - comments: 1.14.0
  - contacts: 4.2.2
  - dav: 1.22.0
  - federatedfilesharing: 1.14.0
  - federation: 1.14.0
  - files: 1.19.0
  - files_external: 1.16.1
  - files_rightclick: 1.3.0
  - files_sharing: 1.16.2
  - files_trashbin: 1.14.0
  - files_versions: 1.17.0
  - logreader: 2.9.0
  - lookup_server_connector: 1.12.0
  - metadata: 0.17.0
  - nextcloud_announcements: 1.13.0
  - notes: 4.5.1
  - notifications: 2.12.1
  - oauth2: 1.12.0
  - password_policy: 1.14.0
  - phonetrack: 0.7.2
  - photos: 1.6.0
  - privacy: 1.8.0
  - provisioning_api: 1.14.0
  - root_cache_cleaner: 0.1.3
  - serverinfo: 1.14.0
  - settings: 1.6.0
  - sharebymail: 1.14.0
  - support: 1.7.0
  - text: 3.5.1
  - theming: 1.15.0
  - theming_customcss: 1.12.0
  - twofactor_backupcodes: 1.13.0
  - twofactor_totp: 6.4.1
  - updatenotification: 1.14.0
  - viewer: 1.8.0
  - workflowengine: 2.6.0
Disabled:
  - admin_audit
  - circles: 22.1.1
  - contactsinteraction: 1.0.0
  - dashboard: 7.0.0
  - duplicatefinder: 0.0.15
  - encryption
  - files_3d: 0.5.0
  - files_pdfviewer: 0.8.1
  - files_videoplayer: 0.9.8
  - firstrunwizard: 2.8.0
  - ransomware_protection: 1.14.0
  - recommendations: 1.1.0
  - survey_client: 1.10.0
  - systemtags: 1.11.0
  - user_ldap
  - user_status: 1.0.1
  - weather_status: 1.1.0

Nextcloud Signing status

No errors have been found.

Nextcloud Logs

-

Additional info

Thanks!

@haarp haarp added 0. Needs triage Pending check for reproducibility or if it fits our roadmap bug labels Nov 10, 2022
@szaimen

This comment was marked as outdated.

@nextcloud-command nextcloud-command added the stale Ticket or PR with no recent activity label Jun 27, 2023
@haarp
Copy link
Author

haarp commented Jul 2, 2023

Nextcloud 27.0.0, bug is still present. Sorry for the delay, @szaimen

Screenshot:

Screenshot_2023-07-02_10-33-29

The first directory was scanned by navigating into it manually, it has the correct timestamp. The other dirs were left to be scanned by Nextcloud.

@haarp haarp changed the title [Bug]: Inconsistent scanning behavior of external storage [Bug]: Wrong metadata due to inconsistent scanning behavior of external storage Jul 2, 2023
@nextcloud-command nextcloud-command removed stale Ticket or PR with no recent activity needs info labels Jul 3, 2023
@nextcloud nextcloud deleted a comment from nextcloud-command Aug 29, 2023
@joshtrichards
Copy link
Member

Sounds like #1583 in essence

@DorraJaouad
Copy link

duplicate of #1583

@DorraJaouad DorraJaouad closed this as not planned Won't fix, can't repro, duplicate, stale Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap 27-feedback bug feature: external storage feature: filesystem
Projects
None yet
Development

No branches or pull requests

5 participants