News for hackers. Stuff that matters.

A comment on The Btrfs inode-number epic (part 1: the problem).

Re:The Btrfs inode-number epic (part 1: the problem) by darknavi on Tuesday August 24, 2021 @05:47PM (#28295396)
I have seen too many posts with users who have had their btrfs pools corrupted for me to try and dabble with it. (Using Unraid specifically).

I'll stick with xfs.

[ Parent | on HN ]
Re:The Btrfs inode-number epic (part 1: the problem) by __david__ on Tuesday August 24, 2021 @06:13PM (#28295642)
Similarly, after I got stuck with a corrupted xfs volume that couldn't be self-fixed or manually fixed (the process would take literal days and then fail in some unhelpful way) I gave up and went back to using ext4 for everything.
[ Parent | on HN ]
Re:The Btrfs inode-number epic (part 1: the problem) by SkyMarshal on Tuesday August 24, 2021 @06:46PM (#28295924)
Why not ZFS or ZoL (https://zfsonlinux.org/)?

B/c it’s not built into the kernel, or some other reason?

[ Parent | on HN ]
Re:The Btrfs inode-number epic (part 1: the problem) by SkyMarshal on Tuesday August 24, 2021 @06:47PM (#28295930)
> I’ll stick with xfs

Why not ZFS or ZoL (https://zfsonlinux.org/)?

B/c it’s not built into the kernel, or some other reason?

[ Parent | on HN ]