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

And they almost always 'forget' to mention "that was in 2010" or "I was using the BTRFS feature marked 'do not use, unstable'".

It's really difficult to get a real feel for BTRFS when people deliberately omit critical information about their experiences. Certainly I haven't had any problems (unless you count the time it detected some bitrot on a hard drive and I had to restore some files from a backup - obviously this was in "single" mode).



My fairly recent experience with some timelines, posted 20d ago: https://news.ycombinator.com/item?id=45210911

Some of the most catastrophic ones were 3 years ago or earlier, but the latest kernel bug (point 5) was with 6.16.3, ~1 month ago. It did recover, but I already mentally prepared to a night of restores from backups...


One of the PostgreSQL devs managed to corrupt Btrfs about 2 years ago when working on async IO. Is that recent enough?




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

Search: