On Thu, Dec 28, 2017 at 08:49:56PM +0100, Adam Borowski wrote:
> On Tue, Dec 26, 2017 at 05:20:58PM -0800, Rick Moen wrote:
> > btrfs is still scarily beta after rather a lot of years of development.

That's what worries me about btrfs.

'''
'''

> 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.

I guess it's time to ask, 

  Where are the corpses buried?

If I were to use btrfs, it looks as if I'd have to know this.

-- hendrik

> 
> But if you do, you get:
> 
> * data and metadata checksums.

That's why I'm leaning toward btrfs.

>  It is scary how inadequate disks' own
>   checksums are, and how often firmware bugs, bad cables, motherboard or
>   hostile fairies cause data corruption.  On ext*, this leads to silent data
>   loss that you then discover months later once backups get overwritten.
>   Out of all my bad disks/eMMC/SD since I started looking at this, that were
>   not total device loss, at least some silent corruption happened in _every_
>   _single_ _case_.  You have for example two sectors the controller reported
>   and 3K other sectors it did not.
> 
> * better chances to survive unclean shutdown than non-cow filesystem.  Ext*
>   can be told to provide an equivalent level of protection but then it needs
>   to write every bit of data twice.

Yes.  At the moment I am actually having it write every bit of data 
twice.  And I still get adequate performance.  Maye this shows how 
modest my performance demands are.

...
...

> 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.

What's needed for maintenance?

-- hendrik

> 
> Another caveat: don't forget to mount with noatime.

I presume that's just a performance issue, not a bug.

-- hendrik
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Reply via email to