Element Reports Disk Full, Becomes Unusable, Restart Requires Relogin

### Steps to reproduce

I'm doing pretty intense disk I/O on this system that might be triggering this, so it could be rare. Element becomes unstable/slow, then eventually says "Element crashed ... something (disk full)."

At this point, if you click around to try and try to do anything, all chats are blank. I can close Element and wait a bit, then reopen it. Sometimes it will just work, other times I have to re-login (which is annoying).

I can tell you my disk is not full (or even close). I think this error is a result of how I'm abusing my system at present, so it's not entirely Elements fault, but I believe it should gracefully handle this better.

### Outcome

What happens; everything breaks and you have to re-open Element / sometimes re-login.

What I'd like to happen; everything breaking is probably unavoidable with what I'm doing (I don't know if this will even affect anyone else) - but it should handle this failure more gracefully. I think some kind of transactional database storage or some method for Element to have a running backup of its own state, so that if the application does crash and burn, the next startup will work cleanly.

### Operating system

Debian 13 "trixie" GNU/Linux

### Application version

Element version: 1.11.109 Crypto version: Rust SDK 0.13.0 (f64839e), Vodozemac 0.9.0

### How did you install the app?

```
# cat /etc/apt/sources.list.d/element-io.list deb [signed-by=/etc/apt/keyrings/element-io-archive-keyring.gpg] https://packages.element.io/debian/ default main
```

### Homeserver

matrix.org

### Will you send logs?

Yes