Fix files on external storages

[AlessioP3]

Hi,
I have run the unsolvable_files.sh script.
The script lists me a list of files, but at this point I don't know how to proceed to fix the files

All these files are on an external drive connected via USB.

Thank you in advance.

[artonge]

How is Nextcloud connected to them? External storage?

[AlessioP3]

Yes, I connected the external drive to nextcloud via the nextcloud application called "external storage support"

[artonge]

The script does not support that currently. Feel free to make a pull request to add support for external storage :)

[AlessioP3]

Thank you for your reply.
Could you please explain what the problem is with these files and tell me theoretically what the script should do to correct the files?

[artonge]

The problem is that the script is not currently able to know where they are located.

While in theory this could be done, it is probably easier for you to take the output of the script and run touch on every listed file.

[AlessioP3]

thank you for the suggestion, I ran touch on the files and the problem was solved.
After a few days, however, the problem returned on other files.

I have identified the client that is generating the problem every time it modifies a file.
In order to understand how to solve the root of the problem, can you tell me what is causing the error?

[artonge]

The desktop client version 3.4.0 included several fixes for the Virtual files feature on Windows. Unfortunately one of those fixes had a side effect that removes the modification time from files and trigger an upload to the server of those files with invalid metadata.

The latest updates of both the client and the server should prevent this behaviour.

[jahill92]

Hello @artonge
Any idea on how to address this issue for external Samba stores?
I have a central external smb store that every user has access to and a user dir external storage configured with $user as share.
Since the SMB access is not transparent to the system I cant run touch on the files.