Adam Borowski wrote (excerpted): > As for its state: btrfs is, well, btrfs. You get both extremely powerful > data protection features you won't want to live without, and WTF level > caveats. I wouldn't recommend using btrfs unless you know where the corpses > are buried. > > But if you do, you get:
> * data and metadata checksums. > * better chances to survive unclean shutdown > ( * faster backup than rsync) > * snapshots to protect from human error > You also get compression, deduplication, reflinks, etc. > Other downside is the need for maintenance. On single dev, you can live > well without, but on multi dev you need to do manually a lot that's taken > for granted with MD. > > Another caveat: don't forget to mount with noatime. If someone would like to crowdfund an engineer to work on this project I would certainly pony up. Even if I don't use btrfs ATM, I would support to it for the sake of the ecosystem. > > Meow! -- Joel Roth _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
