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.

How old are you?

Are you using zfs?

That really is one hell of a hot take 😀

I for one really love the zoomed out preview on the right that has become popular in recent years.

https://jason-williams.co.uk/assets/img/2020/debugging_screenshot.png

Really hard to do in a terminal. If you have errors you can see very fast where they are located/clustered in the file and can already tell just by the shape of the program where it is.

Another example: GUI color picker directly in my editor as a tooltip above color values in css/html templates.

Another example: inline preview of latex or Template fragments.

But it’s a gigantic waste of energy and time when you could just download a 2mb package and be done with it.

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

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?

Replace Debian apt sources with Ubuntu ones, do system upgrade and install the Ubuntu-Desktop package, now you have Ubuntu.

It’s been a while since I have done this, but it’s totally possible.

We did this transition from Ubuntu to Debian at Work with thousands of workstations.

It requires a bit of time and testing but it’s possible.

For a handful of servers, try zabbix. Every distribution has a packaged zabbix agent. It has everything: web ui, a way to Auto discover things with a bit of setup, nice graphs, alerting, LDAP User Management if you need it, a way to define per person/group alerting/notification schedules. And the community is big enough that many common services (fail2ban/postfix/MySQL/etc.) have premade custom monitoring scripts. Adding your own metrics is also very easy.

Not really. You can still use dm-verity for a normal raid and get checksumming and normal performance, which is better and faster than using btrfs.

But in any case, I’d recommend just going with zfs because it has all the features and is plenty fast.

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.

For personal use, I don’t bother with databases on k8s. They are waaay easier to manage if you just let your host distribution run it as a regular service and Upgrade it through that

Most of the time, it’s enough to copy the whole EFI partition to the new machine and update whatever boot entries are in there to point to the right new partitions.

In case of a switch to something like zfs, it’s a bit more involved and you need to boot a live Linux, chroot into the new “/” with /boot mounted and /dev, /proc, /sys bind mounted into the chroot.

Then you can run the distro-appropriate command to reinstall/ update grub into the EFI partition and they will usually take care of adding the right drivers.

Btrfs is in the mainline kernel since 2.6.29, that’s 14 years ago my friend 😃

It’s included in every major distro for a long long time.

I disagree, you usually just need to get /boot and your EFI things right on the new disk, rsync stuff over and fix any references to old disks in /etc/fstab and maybe your grub config and you are done. I have done this migration>10 times over the years onto different filesystems, partition Layout and raid configurations and it’s never been particularly hard.