On Fri, Feb 05, 2021 at 06:59:05PM +0100, donoban wrote: > On 2/5/21 5:24 PM, Jinoh Kang wrote: > > Possible solutions would be: > > > > - Patch dm-thin. Now to implement this properly, dm-thin must first > > slice the range, have it ref'd somewhere and then issue discards (so > > that it can handle power disruptions). > > - Switch to reflinks. BTRFS has been around 10+ years, so I assume it's > > stable enough? > > > > I've been using BTRFS for a few years now and haven't had any problems > except some CPU bottleneck using send/receive, but probably you are not > interested in that functionality.
I'd like to see btrfs added for its checksums as well. I've personally had `btrfs scrub` catch hardware problems before more data got silently corrupted. -- https://petertodd.org 'peter'[:-1]@petertodd.org -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/20210211050651.klk6xdr4bdxohvj2%40petertodd.org.
signature.asc
Description: PGP signature
