3 ms·
Big concern I've seen is around btrfs being the default. I was concerned too, especially with the old versions losing data, but I've heard that a ton of work h
by freedomben 6y ago
Big concern I've seen is around btrfs being the default. I was concerned too, especially with the old versions losing data, but I've heard that a ton of work has gone into btrfs and it's maturing/stabilizing nicely.
Has anybody used a recent (last couple of years at the most) btrfs as their main filesystem who can comment on how it has been?
- sebiw 6y agoI am running Btrfs on about a dozen machines (solid state and spinning disks). All of them are servers and run "business-critical" stuff. No issues during the last 2 years, everything flawless. The ability to scrub your data and have strong data integrity guarantees is just one of the benefits of Btrfs. I'm also using transparent compression (GZIP and ZSTD) and even RAID1 (disk replacement procedure worked flawless last time I had to use it). For workloads such as MariaDB (heavily updated-in-place files) you may want to go ahead and disable CoW features, though. This leaves you without data checksumming (InnoDB uses it's own checksumming - not losing much there) but you still get a lot of the other great Btrfs features.
- jbrnh 6y agoI used to run a couple of hundred servers and workstations with SLES and openSUSE with btrfs for /. Just SUSE's vanilla supported setup, and user data on smb/nfs filers. I tended to forget that btrfs was even involved. I can't remember a single time btrfs gave us any trouble. But snapper snapshots saved a customers ass on one or two occasions.. That was several yeas ago. I also imagine that btrfs has only improved since then.