Miscellaneous .DS_Store files from macOS Finder, rclone complains each sync

Help and Support
1

What is the problem you are having with rclone?

After running sync I get multiple errors of this kind

NOTICE: .DS_Store: Skipping undecryptable file name: illegal base32 data at input byte 0

I want to make completely sure how I can safely delete these macOS Finder .DS_Store files. I guess they’re an artifact from browsing the encrypted rclone destination with Finder.

The target of this specific backup does not currently have a second backup so I want to be completely sure no dataloss happens.

So, how can I be completely safe in deleting these specific .DS_Store files? I have my own ideas, but I do not wish to risk any dataloss or corruption from messing with potential indexes, directory structure or any such thing rclone might do on its own.

……………………………………………………………………

Run the command 'rclone version' and share the full output of the command.

rclone v1.72.1 (Windows)

Which cloud storage system are you using? (eg Google Drive)

Crypt remote to local NAS.

The command you were trying to run (eg rclone copy /tmp remote:tmp). -->

rclone sync e: encryptednasbackup: --bwlimit 100m -P --exclude="/System Volume Information/" --exclude "/$RECYCLE.BIN/**" --delete-after

A log from the command that you were trying to run with the -vv flag

Summary:

ERROR : Attempt 3/3 failed with 2 errors and: not deleting files as there were IO errors

and

NOTICE: Failed to sync with 2 errors: last error was: not deleting files as there were IO errors
2

fwiw, on windows, use e:\, never e:
can easily lead to a disaster.

is that file crypted or not?

3

It’s placed by macOS Finder app. I guess this whole question really is silly and I can simply remove it, i just wanted to be sure.

I’ll also get e: changed to e:\, thank you.

I do wonder though if rclone has any built in command for deletion? In case something ever did go wrong and would require it.

4

macos is adding a decrypted file info a folder with encrypted files.
so it would make sense about that rclone error.

as for a solution or workaround, maybe @kapitainsky knows...