cablespaghetti.dev is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
Another data corruption, fortunately not fatal, with btrfs. Two mirrored disks that have little activity. On the same server, Proxmox 9, there is also a ZFS pool (mirrored, more active). Same type of disks.
An employee mistakenly connected an electric heater to a socket protected by the UPS, and the server rebooted brutally.
Upon reboot, one of the two btrfs disks reported:
[ 167.015266] BTRFS error (device sdd): parent transid verify failed on 873906176 wanted 998679 found 998677
[ 167.017007] BTRFS error (device sdd): parent transid verify failed on 873906176 wanted 998679 found 998677
[ 167.052517] BTRFS error (device sdd): open_ctree failed mount: /btrfs: can't read superblock on /dev/sdd.
Result: unable to mount, even in degraded mode. The only way was to disconnect sdd and mount the other disk in degraded mode.
No issues with the ZFS pool.
Needless to say, I'm now copying the data to ZFS, and before tomorrow, these two disks will be a new ZFS pool.
I prefer to have automatic updates and the longterm #kernel ;)
#BTRFS broke once, the "stable" kernel had tons of unrelated breakages that only came to light when #Fedora, #Tumbleweed and #Archlinux broke.
Filesystem + #LVM + #LUKS is such a crazy complexity. From the perspective of someone who needed to backup and restore such a partition.
#BTRFS + LUKS is way easier and very stable. Linux broke everywhere for me in the past, but never BTRFS (when using the longterm kernel, there were some broken drivers in the "stable" kernel a short while ago)
Filesystem-based encryption (RIP #bcachefs) would reduce this even more. But luckily my NixOS with bcachefs install didnt boot back then, otherwise I would have needed to reinstall.
I'm sure this will be fun for the next person to grok what cursed thing I've done.
Filesystem Size Used Avail Use% Mounted on
/dev/sda 3.5T 5.8M 3.5T 1% /data
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 1.7T 0 disk /data
sdb 8:16 0 1.7T 0 disk
Even more fun - `lsof /dev/sdb` returns nothing and doesn't show up as mounted with `mount`.
I tried tuning various parameters but after some reading came to the conclusion that lots of small files with very little RAM is about the worst case scenario for XFS.