Constant high-cpu usage despite nothing is syncing up about onedrive

[abraunegg]

@DawidIzydor
What does onedrive --version give as this information is lacking in your post

[DawidIzydor]

onedrive v1.1.4-2-g15b4730

Looking thorugh the code as of now to check for local changes onedrive looks through each and every of files to check their last modified date.

Couldn't it use something like find -cmin -600 instead (based of timestamp of last sync)? This executes in under a second on the same dataset

[abraunegg]

@DawidIzydor

onedrive v1.1.4-2-g15b4730

OK - you will be hitting a known issue that has been fixed to do with the DB and indexes.

Also the 'skilion' client does not receive any support (reference) and contains issues / defects that put you at risk of data loss. Despite a new version release in Oct 2020, these defects remain. If you wish to use a client which is fully supported please refer to: https://github.com/abraunegg/onedrive

Major differences / Enhancements:

• Existing bugs with the 'skilion' client fixed
• File upload / download validation to ensure data integrity
• Support Real-Time syncing of remote updates via webhooks
• Supports Shared Folder support for OneDrive Personal and OneDrive Business accounts
• Supports SharePoint / Office365 Shared Libraries
• Supports Desktop notifications via libnotify
• Supports Dry-run capability to test configuration changes
• Prevent major OneDrive accidental data deletion after configuration change
• Supports National cloud deployments (Microsoft Cloud for US Government, Microsoft Cloud Germany, Azure and Office 365 operated by 21Vianet in China)
• Supports single & multi-tenanted applications
• Supports rate limiting of traffic
• Support for Docker
• Support for Podman

Suggest that you:

• Uninstall your current installed client then install from the OpenSuSE Build Service the correct package for your platform
  • Make sure it is uninstalled and no 'onedrive' binary exists before you install the correct package - otherwise you will end up with 2 binaries in your search path ... the old and new .... which is not ideal

[DawidIzydor]

Thanks, this fixed the issue