173
btrfs appreciation post (lemm.ee)
submitted 1 year ago by geoff@lemm.ee to c/linux@lemmy.ml
21 comments fedilink hide all child comments

cross-posted from: https://lemm.ee/post/4274796

Just wanted to share some love for this filesystem.

I’ve been running a btrfs raid1 continuously for over ten years, on a motley assortment of near-garbage hard drives of all different shapes and sizes. None of the original drives are still in it, and that server is now on its fourth motherboard. The data has survived it all!

It’s grown to 6 drives now, and most recently survived the runtime failure of a SATA controller card that four of them were attached to. After replacing it, I was stunned to discover that the volume was uncorrupted and didn’t even require repair.

So knock on wood — I’m not trying to tempt fate here. I just want to say thank you to all the devs for their hard work, and add some positive feedback to the heap since btrfs gets way more than it’s fair share of flak, which I personally find to be undeserved. Cheers!

top 21 comments
sorted by: hot top controversial new old
[-] exu@feditown.com 34 points 1 year ago

Agreed, RAID 1 (and 10) are pretty stable.

Moderately fun fact, RAID 1 in BTRFS is not really RAID 1 in the traditional sense. Rather it's a guarantee that your data lives on two separate drives. You don't know which ones though. You could have one copy of everything on a 12TB drive, whith various secondary copies distrivlbuted on three 4TB drives.
Traditional RAID 1 works ONLY with two drives, with a capacity of the smaller drive as upper limit. The way to extend a traditional RAID 1 array is by adding two new drives and creating a RAID 10 with all four. (Multiple RAID 1 striped)

[-] geoff@lemm.ee 12 points 1 year ago

This right here is what has made it so flexible for me to reuse salvaged equipment. You can just chuck a bunch of randomly sized drives at it, and it will give you as much storage as it can while guaranteeing you can lose any one drive. Fantastic.

[-] flux@lemmy.world 10 points 1 year ago

Anything specific advice you would give to others to prevent corruption? Or keep drives healthy?

[-] lemann@lemmy.one 9 points 1 year ago

Schedule a monthly scrub (with the foreground option), and make sure you get notified if the exit code is non-zero

https://btrfs.readthedocs.io/en/latest/btrfs-scrub.html

I also have a weekly balance scheduled to keep block groups compact, although if you don't frequently delete files this may not be necessary IMO

[-] geoff@lemm.ee 2 points 1 year ago

I’m not sure I know enough to be giving out advice, but I can tell you what I do. I do have a cron job to run scrub, to keep the bitrot away. I also tend to replace my drives proactively when they get REALLY old — the flexibility of btrfs raid1 lets me do that one drive at a time instead of two, making it much more affordable. You can plan out your storage with the btrfs calculator.

[-] blashork@hexbear.net 8 points 1 year ago

I'm glad it' working well for you, but I don't think it' true to say that btrfs gets beyond its fair share of flak. It gets the exactly correct amount of flak for what it is. Every place I have worked at that wanted to deploy a COW fs on like, a NAS or server, has always gone with zfs. btrfs is such a mess it never even enters the conversation. Even if it can have its bugs ironed out, the bcache dev was right in pointing out that its on disk formats are poorly designed for their job, and cannot be revised except in a new version of the entire fs. I hope bcachefs gets merged into the kernel next year, that's a filesystem I would actually trust with my data.

[-] ProtonBadger@kbin.social 8 points 1 year ago* (last edited 1 year ago)

Btrfs does get a lot of flak based on hearsay or experiences that are out of date. It works well in a lot of scenarios and is used a lot now, ZFS is also a good fs for many use cases, especially in enterprise situations.

I can't comment on the on-disk formats as I have no experience there but Btrfs works well in a lot of use cases for for a lot of users.

Bcachefs sounds promising but it does have a long way to go and will need a lot of testing. It's getting into the kernel to get more testing mileage on it and encourage more developers, it only have one guy working on it (except for the casefolding submission) which is a big problem for both present and future. Hopefully it'll get more devs interested.

Never trust any filesystem, or the storage media. Consider anything that holds your data to be fallible.

[-] GnuLinuxDude@lemmy.ml 7 points 1 year ago

I've been using it in Fedora since they switched to it as the default FS. I have not done anything special. I am not trying anything fancy except compress-force=zstd:1. Seems good to me!

[-] deadcatbounce@reddthat.com 1 points 1 year ago

Why just :1? The default is :3 and looking at the timings for zstd deflate speed vs compression level (Google for it .. ), becomes slow at around 7.

Don't mean shit to me but suggest you reconsider.

[-] GnuLinuxDude@lemmy.ml 1 points 1 year ago

Slow relative to what? Any zstd compression, while really fast, will be slower than native write speeds to my nvme. A tiny bit of ratio gain isn't worthwhile to me.

[-] Grass@geddit.social 5 points 1 year ago

I use it on my steam deck microsd to cram more shit in via compression. Main drive is left as ext4 though so case folding can be used for particularly janky windows games or mods.

[-] lloram239@feddit.de 5 points 1 year ago

Same experience for me, except without the RAID. It's the only file system I ever used that just worked and didn't self destruct. With ext234 I always ended up with all my files scattered in lost+found sooner or later. In the early days XFS couldn't handle system crashes without deleting important files and I even managed to corrupt ZFS on an USB drive. Never had anything catastrophic happen with BTRFS, quite the opposite, it warned me of broken RAM or drives a few times.

That said, BTRFS can get a bit finicky when it gets full. It has gotten a lot better over the years, but it's a situation that one should better avoid.

[-] Revan343@lemmy.ca 1 points 1 year ago

I've been wanting to build a raid for a while, what raid controller do you use/would you recommend?

[-] geoff@lemm.ee 2 points 1 year ago* (last edited 1 year ago)

For a software RAID like this, you don’t want a hardware RAID controller, per se – you just want a bunch of ports. After my recent controller failure, I decided to try one of these. It’s slick as hell, sitting close to the motherboard, and seems rock solid so far. We’ll see!

this post was submitted on 14 Aug 2023
173 points (97.8% liked)

Linux

48740 readers
1211 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz