Pretty much every alerting system I know also has a filter option to only apply automated discovery rules to certain filesystem types.

But yes, most don't first squashfs or mounted read-only snapshots by default and it sucks.

In Germany we need coins to unlock supermarket carts, so I use the coin pocket for it’s intended purpose to house my one coin.

They sure have Nazis in Ukraine as has every country.

But saying that the fascists in Italy have anything to do with Ukraine needs very good evidence to support such a wild claim.

You can’t trust any full disk encryption without it because only a TPM can verify that your bootloader and initrd are not compromised.

Because he has a lot of nerdy friends that use signal? Same reason anyone else would choose one messenger over another i’d guess.

Not much difference because both signal and WhatsApp use the same protocol and encryption.

What’s the problem with that script? That’s such a basic use case and not very hard to do at all in systemd.

Where do you struggle with it? Can we maybe help with something?

From arch wiki:

Disabling CoW in Btrfs also disables checksums. Btrfs will not be able to detect corrupted nodatacow files. When combined with RAID 1, power outages or other sources of corruption can cause the data to become out of sync.

No thanks

If you are planning to have any kind of database with regular random writes, stay away from btrfs. It’s roughly 4-5x slower than zfs and will slowly fragment itself to death.

I’m migrating a server from btrfs to zfs right now for this very reason. I have multiple large MySQL and SQLite tables on it and they have accumulated >100k file fragments each and have become abysmally slow. There are lots of benchmarks out there that show that zfs does not have this issue and even when both filesystems are clean, database performance is significantly higher on zfs.

If you don’t want a COW filesystem, then XFS on LVM raid for databases or ext4 on LVM for everything else is probably fine.