Comment on Issue: The limits of the cloud?
pepecyb@hub.hubzilla.hu@hub.hubzilla.hu 2 weeks ago That also seems rather unlikely, although the thought had crossed my mind too.
Example:
I upload the image A.png (a completely new image) to the “Artikelbilder” folder and embed it in a post: after a short while, the hub freezes and displays the error message in the log.
After rebooting, I delete the post and the image.
Then I upload the image A.png again to a different directory and use it in a post: no error occurs.
I upload a completely new image, B.png, to a different directory and use it in a post: no error occurs.
I upload the image B.png to “Artikelbilder” and use it in a post: after a short while, the hub freezes and displays the error message in the log.
Reboot, delete…
I move the image B.png from the other directory to “Artikelbilder” and use it for a post: after a short while, the hub freezes and displays the error message in the log.
The only thing that might explain this is that the issue does not occur with older images already present in the critical directories.
Example:
I upload the image A.png (a completely new image) to the “Artikelbilder” folder and embed it in a post: after a short while, the hub freezes and displays the error message in the log.
After rebooting, I delete the post and the image.
Then I upload the image A.png again to a different directory and use it in a post: no error occurs.
I upload a completely new image, B.png, to a different directory and use it in a post: no error occurs.
I upload the image B.png to “Artikelbilder” and use it in a post: after a short while, the hub freezes and displays the error message in the log.
Reboot, delete…
I move the image B.png from the other directory to “Artikelbilder” and use it for a post: after a short while, the hub freezes and displays the error message in the log.
The only thing that might explain this is that the issue does not occur with older images already present in the critical directories.
Nor did the method of referencing in the source code (i.e. <HUB>/photos/<HASH_FILENAME> or <HUB>/cloud/<CHANNEL_NAME>/<REAL_FILENAME>) make any difference. New images from the two problematic subdirectories caused the system to freeze, whilst images from other directories did not. I’ve now simply stopped using those two directories for new uploads… but that's obviously just treating the symptoms.
Performance differences when accessing new vs old files does not make much sense to me though :person_shrugging:
That’s exactly why I’m confused. The only thought I had was whether it might somehow be down to the number of entries in the directory. However, the two directories do differ in the number of entries. What they have in common is the rather large total size (MB). I’ve no idea at the moment.
I’ll get back to you as soon as I have the results.