The mobile and TV clients are often limited to the codecs with hardware acceleration. Or just selecting a lower bitrate on the client will cause transcoding.

There is an even more relevant video of using external storage trough USB. He recommends using software raid:

Can We Build a Home Server Out of Mini PCs?

Are both drives fully encrypted with LUKS? Is trim enabled in both crypttab and fstab?

Thanks for the links! I updated my config from z3fold to zsmalloc and adjusted the vm.page-cluster to test these out.

Reading a bit more, I think when using large max_pool_percent (>30) with Zswap the two solutions are more similar than not. A crucial difference is what use-case is more acceptable since Zswap can cause unresponsiveness (and potential lockup) under high memory pressure. While Zram could result in an OOM crash in a similar worst-case scenario.

Btrfs with compression enabled and subvolumes set.

And enable/automate maintenance services for BTRFS. For example: balace should be run on heavily used system disks or scrub could help detect errors even on single disks.

ZRAM (With proper sysctl.conf like PopOS does).

Could you explain the preference of ZRAM over ZSWAP? I thought the latter was the more advanced and better performing solution. Is there some magic in Pop’s config?

Happy to help! Tough you are right, this is a rather generic error that doesn’t help much just confirms that the GPU is the issue.

At this point it could be a driver issue since there are similar open bug reports. A hardware problem is still possible since you previously said that it’s unstable on windows too, and power related issues can also lead to this error message.

Most distros use systemd and its logging solution: journald. You can use journalctl to read the logs around the time of the crash for e.g.:

• journalctl -S -5m this shows the last 5 minutes. Use this when a game crashes but the system continues working and did not reboot.
• journalctl -b -1 -S -10m this shows the last 10 minutes from the previous boot. Use this if the crash froze the whole system and rebooted.

Look for red lines (errors) and what wrote them. AMD GPU faults usually have the ‘amdgpu’ mentioned, memory errors could appear as ‘protection fault’.

Did you check the system logs to see what caused it?

Many things can result in seemingliy random crashes. Any overclock (including XMP and Expo) or undervolt or even a bios version can be problematic.

I would check first if it’s stable on windows.

What filesystem are you using? Is it encrypted?

Could you run a benchmark to verify if reads and writes are both affected? KDiskMark is like crystaldiskmark or Gnome Disks has a built in benchmark.

Do I need to disable compression on my swap subvolume?

Short: No

Long: it doesn’t matter when mounting multiple subvolumes of the same btrfs partition the options from the first one (usually /) will apply to all. So even if you disable it, that will be ignored.

The old way of creating swap shows the chattr +C line which disables CoW. The same method should work for your Downloads folder since CoW is needed for snapshotting.

You’re right, I linked an old article and it should have been fixed, but there are newer reports of remaining issues. But even this should be fixed in your kernel version already so it was probably a bad guess.

There were issues with TPM so that might affect the older bios versions. You could try disabling it.

I’m not 100% sure, but for me it caused a similar “freezing” or unresponsive experience when the daily cleanups run in the morning. If there was a freeze after every (even short) sleep and resume that might be a different issue.

Yeah it’s disappointing that such an annoying bug is still present and quotas are enabled without warnings. You could continue using Timeshift, the only feature quotas provide is the individual disk usage of the snapshots.

Anyone looking for the solution: https://www.suse.com/support/kb/doc/?id=000020696

What did you use to manage snapshots? For e.g. timeshift enables quotas and that can cause freezes when deleting old snapshots.