![](https://aussie.zone/pictrs/image/2644a4fe-cce3-4126-b80b-40e6369976d1.jpeg)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
Yeah, I’ve gone over 24 hours now without it occurring… but not calling it “fixed” until at least a week.
I also have backup accounts on these instances:
https://beehaw.org/u/lodion
https://sh.itjust.works/u/lodion
https://lemmy.world/u/lodion
https://lemm.ee/u/lodion
https://reddthat.com/u/lodion
Yeah, I’ve gone over 24 hours now without it occurring… but not calling it “fixed” until at least a week.
I’ve been seeing similar since upgrading to 0.18. Upgraded to 0.18.1-rc.9 yesterday… haven’t seen it reoccur again… yet.
Here is an example I happened to be at my PC for:
Your instance must be very new, very few users, very inactive… or all of the above. I stood up aussie.zone just under a month ago, Postgres DB is currently 9.6GB.
I’m using S3FS to achieve the same thing, but without modifying the ansible config or using native object storage within pict-rs.
I like their sense of humour. The definitely don’t take themselves too seriously.
Good bot.