[mk01]

@mehlvogel

this is because btrfs is checksumming data and metadata and checking with each read & write operation. so what happens is that if clock is too high and the bits get's messed up (doesn't matter if lets say during read or write) btrfs realizes that and remounts filesystem as readonly. you don't see this happening but as this happens system will fail to boot (because writes are essential during boot - for tmpfs creation, lock, status and socket files etc).

so for you us it looks like a fatal error (not booting) but in reality it saved you filesystem from corruption (because of RO no damaged data metadata gets written down). this is also the reason while since btrfs change we see so few reports on messed up filesystems. more it is like failing to start.

in contrast with ext4 for instance, corrupted structures (or 'only' data) gets written / read silently to the filesystem - clearly leading to disaster sooner or later - without indication - so you may think that fine, OC is good and stable. but this is not right.

from my experience OC like [ 900 ] [ 400 ] [ 450 ] [ 2 ] is quite stable and experience very little different from Turbo.