Chat, should I try reformatting my main partition to use #ZFS or #Btrfs?

I'm currently using ext4 (ik, ik) on #NixOS.

Introducing #container‑snap. It's a prototype plugin for atomic OS updates via #OCI images! It integrates with #openSUSE’s tukit and #Podman’s #Btrfs driver to boot your host from a container image. Check out this #oSC25 talk. https://youtu.be/u_9BoxsHQI8?si=l1TqCBmHQWidDc-x

For a #homelab/#selfhosted project, would there be any reason to pick one of #freebsd or #openbsd ? (Just because #netbsd seems amazingly portable it also interests me).
So far I mostly run #Linux containers with #podman and VMs with #proxmox, the only *BSD VM running is #opnsense. And so far #btrfs seems pretty good alternative to #zfs.
I hear the network stack is supposed to be better and the system overall more “unified” but I fail to see what to try or do with it.

OK, riddle me this, #Linux (specifically #ArchLinux) fans.

You can use #ZFS and #btrfs on root to create snapshots before updating the OS. But you can't snapshot EFI, because that's on a separate FAT32 partition.

So what happens if you run an update (pacman -Syu in this case) that includes a kernel update, and something goes wrong? The version of the kernel in the EFI partition will be newer than the modules in the snapshotted /usr/lib/modules. That's surely going to cause an issue, right?

From memory (it's been over 15 years), Gentoo can have multiple versions of the same kernel installed at once. But Arch only allows one version of any package at one time.

Eso de emplear tiempo en el mantenimiento del sistema operativo no es para mí.

I use #btrfs since many years, without any problem. Snapshots and subvolumes, "offline" deduplication, compression, everything works like a charm. Even when I used kernel 4.9.
I can't understand the world of Red Hat rejecting this filesystem. And using… systemd

I guess it's time to finally decide (currently leaning towards 1)...

#nas #btrfs #zfs

dear lord another one, everybody read up to avoid losing data

https://blog.fyralabs.com/btrfs-corruption-issues/

#tech #linux #btrfs #advisory #fedora #ultramarinelinux

Frage an die Schwarmintelligenz: Gibt es bei #btrfs interne Statistiken die verwendet werden können, um die größten "Speicherfresser" zu finden? Ohne du -sk machen zu müssen was über jede einzelne Datei geht?

I'm getting the itch of building my next linux install using #systemd #confext and #sysext.

Basic point, memory of #ansible keeps getting further. Can build out #btrfs subvolumes that are mounted read only. No modification of the /usr or even /etc necessary.

https://man.archlinux.org/man/systemd-confext.8.en

1/2
@_RyekDarkener_ If you want to push #LLM to their limits, here is a prompt about my #BTRFS #RAID5 file server.
All the description is true. I did not expect any useful answer from any LLM. This was inspired by a crazy page that I saw on Reddit
https://www.reddit.com/r/btrfs/comments/1irpwpj/speeding_up_btrfs_metadata_storage_with_an_ssd/
https://usercomp.com/news/1380103/btrfs-metadata-acceleration-with-ssd

Des personnes par ici ont de l'expérience avec l'utilisation combinée de #bcache et #btrfs ?
Vous auriez des retours d'expérience et conseils / recommandations ?

C'est pertinent comme cache en lecture (surtout) si on a une asymétrie du style 500Go de SSD pour >10To de HDD ?
Il me semble que pour mon cas d'usage c'est la lecture aléatoire qui est la plus pénalisante.

1/3

"Error removing device ... Input/output error"
Yeah, thanks #BTRFS, that's why I'm trying to remove it.

I have a bunch of old documents on my computer separated in an "old documents" folder. Currently they are not compressed.
If I compress my "old documents" into a tar.zst archive, will I increase to decrease the probability of them becoming corrupted?

My home partition is using BTRFS if it matters. #BTRFS

A few months ago I wrote a script for work to help users recover files they accidentally deleted from our VAST storage system (using snapshots). I finally re-wrote it for home use with #Snapper snapshots on #btrfs

https://codeberg.org/joatca/oops

Back on #BTRFS after #XFS / #GRUB caused boot failures. First it would work on about every 6th attempt, now it didn't work at all. I'll just mount it with nodatacow, that should give Good Enough TM performance.
Also set up a watchdog a delayed reboot after panic, just to be safe. Should probably also set up a GRUB fallback in case a #NixOS update breaks booting again...