3 ms·
I keep hearing this, with no reference whatsoever to _when_ you had issues with it. Meanwhile distros like Fedora or Synology on their NAS have been running BT
by sph 4y ago
I keep hearing this, with no reference whatsoever to _when_ you had issues with it.
Meanwhile distros like Fedora or Synology on their NAS have been running BTRFS for a while, and there is not much evidence of these legendary data corruption moments.
Last time I posted this comment on a similar anecdote, I got no response. Do you have more evidence to show how fragile btrfs is in 2022?
Because from where I stand it they read like horror stories from users when the btrfs code was very new and unstable, and then echoed ad nauseam by other people. See the sibling comments for example.
- ok123456 4y agoThis was last year. I'd be surprised if it got much better in 12+ months.
- sph 4y agoWere you using BTRFS in RAID mode by any chance? Have you opened a kernel bug report?
- ok123456 4y agoNo. Report what? The stack trace saying the extent tree is bad? There are always going to be consistency errors when you're dealing with filesystems, especially when you're non-ECC memory. They need to be robust enough that the fsck tools can resolve that. From my experience with BTRFS, doesn't do that.