I switching to BTRFS recently, but found myself even more fucked when my system stopped working suddenly and I didn’t know how to fix it without reformatting and installing grub again. Actually lost even more than I would have otherwise just because I wasn’t knowledgeable enough to get any form of recovery to work. That first EndeavourOS install didn’t last 2 months sadly.
Yep, everyone goes through that the first 2 or 3 installs, until you learn how CoW FSes work. It’s not like anything else and it takes a while to master it, but once you learn how to use it, you don’t reinstall ever again, just roll back snapshots 😉.
My least favorite part was needing to use it every time they shipped a kernel update because it broke the Nvidia drivers. Eventually I just pinned my kernel version but it didn’t feel sustainable so I swapped back to Ubuntu, which at least in theory tests against the supported drivers. Ubuntu has its own issues so I’ll probably swap again next time my system needs surgery.
I agree cow + snapshot is pretty useful. I would just never use btrfs for data I care about. There is a reason no one sane runs it in production. Your computer and data do what you want 😊🙂😊.
Cool I had no idea. I like zstd from them. I don’t really want to argue if it works for you that’s great. I’ve seen so many problems with corruption that I wouldn’t recommend it. I guess I’ll give it another try in a VM some day. I really tried to move to it before migrating back to zfs land. I do recall the send and receive working pretty flawlessly. Also was a huge fan of duperemove.
Do you know if it has support for something like zvols yet?
Yes, it did have problems a few years ago, especially regarding RAIDs, but it’s improved a lot since then. RAID5 still sucks though 😁… but I read the problem is finally been worked on (haven’t checked code, I read about it in a sub on reddit).
No, it doesn’t have something like zvol, it has the regular subvolumes (pools in ZFS) and you can assign quotas, the same as in ZFS. But, to represent itself as separate block device, no. And I don’t think this is something that’s planned, though I could be wrong (as I said, I haven’t looked at their git in ages).
BTRFS is your friend guys and gals ☺️.
I switching to BTRFS recently, but found myself even more fucked when my system stopped working suddenly and I didn’t know how to fix it without reformatting and installing grub again. Actually lost even more than I would have otherwise just because I wasn’t knowledgeable enough to get any form of recovery to work. That first EndeavourOS install didn’t last 2 months sadly.
Yep, everyone goes through that the first 2 or 3 installs, until you learn how CoW FSes work. It’s not like anything else and it takes a while to master it, but once you learn how to use it, you don’t reinstall ever again, just roll back snapshots 😉.
Yup. Being able to run my home and root(s) in separate subvolumes, and simply booting into a specific root with a kernel parameter… 😌
I had that on my phone some ten years ago. Ah, the memories. It sucked, though.
Yeah, BTRFS sucked 10 years ago 😂. Try it now, it’s much more stable.
Snapshots 4 life
Mhm, pretty much. I haven’t reinstalled since I started using snapshots.
My favorite part of using Suse was Snapper.
My least favorite part was needing to use it every time they shipped a kernel update because it broke the Nvidia drivers. Eventually I just pinned my kernel version but it didn’t feel sustainable so I swapped back to Ubuntu, which at least in theory tests against the supported drivers. Ubuntu has its own issues so I’ll probably swap again next time my system needs surgery.
I’ve lost so much data to btrfs disk mirrors. Zfs is my friend now.
Meeh, anything that is CoW and has snapshots will do the job, ZFS or BTRFS, whatever rocks your boat 🤷.
I agree cow + snapshot is pretty useful. I would just never use btrfs for data I care about. There is a reason no one sane runs it in production. Your computer and data do what you want 😊🙂😊.
It’s being used in Meta 🤨… in production.
Cool I had no idea. I like zstd from them. I don’t really want to argue if it works for you that’s great. I’ve seen so many problems with corruption that I wouldn’t recommend it. I guess I’ll give it another try in a VM some day. I really tried to move to it before migrating back to zfs land. I do recall the send and receive working pretty flawlessly. Also was a huge fan of duperemove.
Do you know if it has support for something like zvols yet?
Yes, it did have problems a few years ago, especially regarding RAIDs, but it’s improved a lot since then. RAID5 still sucks though 😁… but I read the problem is finally been worked on (haven’t checked code, I read about it in a sub on reddit).
No, it doesn’t have something like zvol, it has the regular subvolumes (pools in ZFS) and you can assign quotas, the same as in ZFS. But, to represent itself as separate block device, no. And I don’t think this is something that’s planned, though I could be wrong (as I said, I haven’t looked at their git in ages).