[Bug]: Can't setup sync directory to reuse existing one if local amount of space less than sync directory size

[Wohlstand]

⚠️ Before submitting, please verify the following: ⚠️

• This is a bug, not a question or a configuration issue.
• This issue is not already reported on Github (I've searched it).
• Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• I agree to follow Nextcloud's Code of Conduct

Bug description

Attempt to login from the scratch and re-use existing directory (left after previous Nextcloud Client installation that was gone due to OS reinstall) causes "no amount space" error.

I already have an entire copy of my server's directory, totally 51 GB, but locally I have 22 GB free space. And thing doesn't lets me to initialise the client if I don't have the free space of equal or more than another copy of my server's directory.

Steps to reproduce

Before

1. Install and configure client.
2. Sync the large directory (my production example has 51 GB).
3. Ensure that space left less than actual size of the synced directory (in my space only 22 GB is left).
4. Close client.
5. Destroy config to make situation like it's a pure installation.

Now

1. Install and try to configure client.
2. Choice "Sync with the server".
3. Select the existing directory (that was been synced previously).
4. Unable to continue, the "Connect" button is inactive, and the "No amount of space in local directory" error is shown.

Expected behavior

I expect that I can select my existing sync directory with no matter how much space is left, even just few megabytes. The only reason to pop-up the "no amount of space" error on attempt to run a new sync from the scratch.

Which files are affected by this bug

none

Operating system

Linux

Which version of the operating system you are running.

Linux Mint 22.2

Package

Official Linux AppImage

Nextcloud Server version

32.0.5, doesn't matter

Nextcloud Desktop Client version

4.0.6, but problem seems exists since 3.17.x, I found no issue on 3.13.4.

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

Fresh desktop client install

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

• Default internal user-backend
• LDAP/ Active Directory
• SSO - SAML
• Other

Nextcloud Server logs

Server logs doesn't matter since it's a client-only problem.

Additional info