>corrupts the instant you use it
>>106868703Sounds like a skill issue.
recovery procedures are pain in the ass for this fs
Stop making shit up.
and since it touts itself as such a superior fs filling your drive with md5's of every chunk gotta make sure that COC_README.doc doesnt change and god forbid one of those md5 blocks or the datta it refers to has a hiccup STOP EVERYTHING NO MORE MOUNTING i smelled a problem i need user spend a week learning about btrfs and running long restore operations that ultimately dont do anything but report to you whats wrong
but hey now you can atleast mount it read only and save a corrupt backup of your shit! just use ext4 like everyone else
>>106868883No I'll use btrfs
>>106868703based on what?mine is still going strong 8 years later.
>>106868703> btrfs ate my dataI doubt this has ever happened to anyone who parrots this nor that a single parrot ever got that idea from a credible source
I never had BTRFS get corrupted. However, due to all of this FUD about BTRFS corruption I switched to ext4. It corrupted with data loss in under 3 weeks of use.
>>106869125fucking kek
>>106868703I heard raid can be problematic, but for home desktop usage, it's perfect. Fedora and openSUSE default to it, sadly only openSUSE has a working rollback option with snapper ootb.
