(Quote)

(Quote)

But, dmidecode --type 16 says "Error Correction Type: None"

I own 3 VMs at HH, IPv6 configuration at LAX & SGP works perfectly for me. I also owned a HKG DC2 nvme VM and IPv6 worked out of the box. I've used the exact netplan config for all my machines

FWIW it works fine for me, this is probably user error tbh.

User error, I checked the wrong email lol.

(Quote)

Turning read-only is not exploding. What you are saying is that keeping to somehow work, like Ext4 and XFS would, letting bad memory chew through your data and FS structures, until the damage is so gr

(Quote)

Btrfs just helped catch the faulty memory. If you used Ext4/XFS, the error would have went unnoticed much longer, and corrupted your data or your filesystem without you knowing. So it is just &quo

(Quote)

(Quote)

(Quote)

to receive mail from Gmail, without any clear error as to why, just the appearance of silently dropped emails. Of course they blame me, inevitably, because they had no idea that MTA-STS was taken so

(Quote)

(Quote)

(Quote)

Reinstall debian 10, and BOOM, VPS can not access and restart/install etc, CPU MEM show "NaN%" and the VNC show "Irgendwas stimmt nicht Error ID:" (Image)

There is still good reason to use Btrfs or ZFS without ECC RAM. It is not going to be any worse than non-checksum filesystems, and it gives you an early warning that RAM is bad. People will ignore the

The roots of that stems from the paranoia that ZFS "scrub" might get confused by an error in non-ECC RAM, and do a "mis-recover" of data from parity, which would ac