The potential risk to ZFS created by the shift in its userbase

Re:The potential risk to ZFS created by the shift in its use... by gst on Monday January 28, 2019 @01:00PM (#19019525)

Is it in maintenance mode? Chris Mason (the main btrfs developer) works for Facebook now and Facebook uses btrfs on "millions of servers" (source: https://code.fb.com/open-source/linux/).

[ Parent | on HN ]

Re:The potential risk to ZFS created by the shift in its use... by DiabloD3 on Monday January 28, 2019 @01:25PM (#19019744)

Facebook's usage of it is very specific, but as you mentioned, Chris Mason (who used to also work at Oracle on their BTRFS team before Oracle dumped BTRFS) is there in-house to make sure it is smooth.

However, I'm pretty sure if I boiled the commit history down for the kernel, most of Facebook's commits would be Flashcache, and not BTRFS.

What I forgot, though, is SuSE supports it as their enterprise FS of choice, which is maybe more important than Facebook.

[ Parent | on HN ]

Re:The potential risk to ZFS created by the shift in its use... by cookiecaper on Monday January 28, 2019 @09:42PM (#19023263)

Yes. It's important to recognize that there's a big difference in one's willingness to adopt a technology if its creator is on staff. Chris Mason's full-time job is to make sure the thing he built works well for his employer.

If you work some place that doesn't have that kind of luxury, perhaps a little extra conservatism is warranted before you go deploying across "millions of servers".

[ Parent | on HN ]