|
|
|
|
|
by traceroute66
618 days ago
|
|
> Facebook (well, Meta, I guess) is famously a big user and developer of btrfs. It seems to work just fine for them I really, really, really wish people would STOP with the whole "it works for $SilconValleyCorp so it must work for me" or "$SiliconValleyCorp does it, so I must". It only leads to disappointment in the case of the former and wholly un-necessary over-engineering in the case of the latter. (a) You do not know *how* or *where* Facebook use BTRFS
(b) Even in the unlikely event they use it "everywhere", they have far more redundancy on every layer than you will ever have. So they don't care if a random BTRFS instance borks itself.
(c) Facebook probably employ the guy who invented BTRFS and an army of kernel developers on top of that .... how much in-house support do you have for BTRFS ?
As far as I am concerned, the fact that they STILL have not fixed RAID5 in BTRFS says everythng you need to know. |
|
(S)he does, their employees explained it many times. They're very public about it.
> So they don't care if a random BTRFS instance borks itself.
They do, according to Christ Mason (IIRC) they investigate every instance of btrfs corruption, regardless of how unimportant the machine and data were. They're not any more frequent than with any other filesystem.
> Facebook probably employ the guy who invented BTRFS and an army of kernel developers on top of that
Not an "army" (only a few developers), but you're correct here.
> they STILL have not fixed RAID5 in BTRFS
Why would they? It's a niche technology that's only interesting to a few home users. I am a home user and have no use for it (or any of the alternatives like raidz).