Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

What does that mean quantifiably?


I’ve used it for about 10 years without consequence; except for problems I had once with enabling experimental options in the kernel module (custom build.) I have used BTRFS exclusively and extensively in terms of what you can do with it since realizing it that many years ago. The only thing I haven’t used is its native RAID support. I think 0 and 1 are fine but I’m not sure about 5/6; parity was still experimental last I checked in 2016 maybe it’s reliable now. Everything else though; compression, snapshots, copy on write, online defrag has all been fine. It is the default for SuSE Leap and Tumbleweed, they use it for snapper (OS snapshots) and BTRFS sub volumes are also supported by Docker for container images and containers. It saves a lot of space when images start to add up.


Synology deploys it in their products


I think it's the default for suse these days.


It is, and openSUSE's default of "create a snapshot before and after every 'zypper in' and/or 'zypper dup'" has saved my bacon on more than one occasion.


SLES explicitly say's just use it for the system NOT Data...there you use XFS.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: