• 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: July 7th, 2023

help-circle


  • exi@feddit.detoLinux@lemmy.mlWhy I dislike snaps
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    10 months ago

    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.



  • exi@feddit.detode_EDV@feddit.deJobs im Linux Bereich?
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    10 months ago

    Da bist du meiner Erfahrung nach aber in komischen Firmen unterwegs. Nach vielen Jahren web Consulting für einen Haufen Firmen habe ich bis jetzt nur bei Media-Saturn PHP auf Windows gesehen und da auch nur bei deren legacy Systemen. Alle anderen waren auf Linux.








  • exi@feddit.detoSelfhosted@lemmy.worldSelfhosted Monitoring Tools
    link
    fedilink
    English
    arrow-up
    0
    arrow-down
    1
    ·
    11 months ago

    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.


  • exi@feddit.detoLinux@lemmy.mlWhat Filesystem?
    link
    fedilink
    arrow-up
    0
    arrow-down
    1
    ·
    1 year ago

    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.


  • exi@feddit.detoLinux@lemmy.mlWhat Filesystem?
    link
    fedilink
    arrow-up
    0
    arrow-down
    1
    ·
    1 year ago

    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


  • exi@feddit.detoLinux@lemmy.mlWhat Filesystem?
    link
    fedilink
    arrow-up
    0
    arrow-down
    1
    ·
    1 year ago

    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.