Facebook To Begin Deploying Btrfs
An anonymous reader writes "After hiring the lead Btrfs developers and Linux kernel block maintainers last year, Facebook is beginning trial deployments of Btrfs. Facebook will start using the next-generation file-system within their web-tier and they will be among the first major public deployments of Btrfs."
and I'll start deploying all kinds of btrfs.
When are they going to make the users of their website tolerable human beings instead of insane caricatures designed to make you lose all faith in humanity?
If Facebook likes something, it must be evil.
> Btrfs
tl;dr, I assume this is a button to let you tag people as a butterface?
(-1: Post disagrees with my already-settled worldview) is not a valid mod option.
FB admins - thank you for paying the developers for the open source work they do. I've been using flashcache with great success in one deployment for almost two years now and am looking to start with hhvm. I didn't even know about the block work.
Obviously kudos to the developers too for spending valuable years on it as well.
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
IMHO, this is a very good thing. btrfs doesn't have as many capabilities that ZFS or Storage Spaces/ReFS possesses.
However, it is finally time that Linux has a filesystem that supports the latest/greatest enterprise features (deduplication and the ability to combat bit rot.)
Realistically, it would be nice to see the native (not FUSE based) code from OpenZFS be included as an alternative, but the CDDL/GPL conflicts likely will make this a no-go.
...and the ship's owner is named Larry Ellison. How do you expect him to be able to afford enough Ole Doc Washington's Patented Yacht Oil to win the America's Cup if he gives nice things away for free??
If only "common" sense was actually that common...
As far as I know, the web tier is basically read-only images of the services to be run. The updates and data are on the back end.
So what, precisely, does using Btrfs in such a deployment prove? It's the stability of modified disks that is in question.
I do not fail; I succeed at finding out what does not work.
Not that anybody'll really notice, but I have a feeling that Facebook's backup and recovery system is queuing up for a stress test.
Having lost data with BTRFS multiple times on my disk array (as recently as last month), I have no confidence in it. The best thing I can say about btrfs is is that it was able to tell me that it had lost data. Not many filesystems do that; but ZFS on Linux has been rock solid for years, and not only tells me if data has been lost, but actually preserves the data as well.
-- Sometimes you have to turn the lights off in order to see.
From wikipedia: Btrfs (B-tree file system) is a GPL-licensed experimental copy-on-write file system for Linux. (I'm sure a lot of people were wondering what it is, since TFA doesn't say)
It would be the biggest "fuck you" in the history of open source if ORACLE licensed ZFS as GPLv3 only, as the license would still be incompatible with the Linux Kernel.
The whole reason the CDDL was chosen by Sun was to be incompatible with GPLv2. Oddly enough, the GPLv3 is incompatible with GPLv2 as well.
From a license persepective, it makes no useful difference, as you'd taint the kernel with an incompatible license to run the code whether it's GPLv3 or CDDL.
-- Sometimes you have to turn the lights off in order to see.
It also has an active development community; the git repo has regular and frequent commits (for a filesystem). ZFS on Linux seems to test more and release less often -- a fact I appreciate as I haven't lost a single bit of data on my ZFS filesystems, but have lost entire btrfs filesystems multiple times. (Yeah, sure, btrfs is "experimental" and will eat your data... so why is Facebook even thinking about using it?)
-- Sometimes you have to turn the lights off in order to see.
There may be such a button, but since the code will be stored on btrfs, it'll corrupt itself in a few months and disappear.
-- Sometimes you have to turn the lights off in order to see.
http://hhvm.com/ from TFSite "an open-source virtual machine designed for executing programs written in Hack and PHP. HHVM uses a just-in-time (JIT) compilation approach to achieve superior performance while maintaining the development flexibility that PHP provides."
There is no right to feel safe thru security vaudeville at the expense of everyone's freedom, privacy and tax money.
next-gen is just marketing propaganda for "new, untested, and hype because it is not old 'X' "
LOL, nice! Or ...
* Broken To Read Free Space
* Broken Treatment Reading Free Space
btrfs FAQ 4.4 - 4.8
* 4.4 Why does df show incorrect free space for my RAID volume?
* 4.5 Aaargh! My filesystem is full, and I've put almost nothing into it!
* 4.6 Why are there so many ways to check the amount of free space?
* 4.6.1 Raw disk usage
* 4.6.2 Actual data
* 4.7 Why is free space so complicated?
* 4.8 Why is there so much space overhead?
https://btrfs.wiki.kernel.org/...
--
Microsoft Windows 8: A 64-bit compilation of 32 bit extensions and a graphical shell for a 16 bit patch to an 8 bit operating system originally coded for a 4 bit microprocessor written by a 2 bit company that can't stand 1 bit of competition with 0 bit of understanding good UI.
next-gen is just marketing propaganda for "new, untested, and hype because it is not old 'X' "
I understand that may apply to Wayland or Mir, but not filesystems, unless you refer to XFS :D
Also, I understand that ZFS is not just a filesystem, as it also covers the functionalities of volume management, kitchen sink, life, the universe, everything, and emacs. Btrfs is a filesystem in the unix philosophy (unless the name refers to 'butterflysystem', in which case it covers all aforementioned functionalities and then some).
Escher was the first MC and Giger invented the HR department.
Larry, really? The guy from the same company who actually STARTED btrfs? That's right, btrfs *is* an Oracle project. Some other big names came onboard later on, but it started there... Check http://en.wikipedia.org/wiki/B...
Microsoft Windows 8: A 64-bit compilation of 32 bit extensions and a graphical shell for a 16 bit patch to an 8 bit operating system originally coded for a 4 bit microprocessor written by a 2 bit company that can't stand 1 bit of competition with 0 bit of understanding good UI.
I am no windows fan but this hoary old cut-and-paste Microsoft/x86 slam is the dumbest fucking ahistorical bullshit and you should be ashamed of repeating it.
1. No part of the x86 family's lineage was ever 4-bit. Despite what you may have heard (from idiots), there is essentially zero compatibility on any level between the 4004 and 8086. There isn't even true compatibility between the 8080 and 8086: although the 8086 was designed to make it easy to port 8-bit 8080 software, Intel did this exclusively at the assembly source code level. Binaries weren't compatible at all. It was, more or less, "Hey, we've got this new 16-bit CPU, but we'll give you 8080-compatible names for the lower halves of 16-bit registers, and 8080-compatible instructions, so if your ASM program only ever uses the 8-bit register names it'll mostly work the same". You still had to make some alterations but much of the program could be used as-is.
2. Even in an alternate reality where the 4004 had a real relationship with x86, QDOS / MS-DOS never ran on it. The 4004 was a calculator and stoplight controller. It never ran anything we'd recognize as an OS. It couldn't address enough memory to do that.
3. No part of the Windows OS lineage was ever 8-bit. The 8086/8088 were 16-bit CPUs with a 20-bit address space, and MS-DOS treated them as such from the very beginning. There has never been a "16-bit patch". If you want to shame Microsoft for something real related to bit depth, do it for how long it took them to ship a 32-bit version of Windows. (386: 1985. Windows '95: 1995. Took them a decade. Shameful.)
4. As of Win 95, it wasn't merely a graphical shell for DOS anymore. If you believe that, sorry, you are wrong.
5. Modern Windows (XP onwards on the consumer side) is derived from Windows NT, which was a completely new OS written from scratch. It is pure unalloyed deliberate thickheadedness to claim that NT is that list of stupid you copypasted -- they made a clean break at the core, and wrote wrapper layers to keep old software working.
Thank you, ladies and gentlemen.
Windows 2000 - from the guys who brought us edlin
1. Sarcasm.
2. Whoosh.
3. MS-DOS, aka, 86-DOS, shares some of the same design of 8-bit CP/M.
* http://en.wikipedia.org/wiki/M...
Do you understand what a File Control Block is??
* http://en.wikipedia.org/wiki/F...
4. a) Incorrect.
* http://en.wikipedia.org/wiki/W...
Also,
* http://web.archive.org/web/201...
b) Win95 contained 16-bit code
* http://en.wikipedia.org/wiki/W...
5. I am quite familiar with the history of Dave Cutler's WinNT 3.1, WinNT 4.0, Win 2000 (aka NT 5.0), WinXP (NT 5.1), Vista (NT 6.0), WIn7 (NT 6.1), and Win8 (NT 6.3) having run/used all of them.
Regardless you completely missed the joke.
Humor. You should try it sometime, instead of being so uptight. You'll live longer, healthier, and happier.
--
First (Public) Contact is coming 2024. Are you prepared for a new larger perspective in the Universe?
Btrfs is fairly comparable to ZFS in terms of capabilities/architecture. Personally I tend to prefer the design (devices go directly into pools - you don't have to designate groupings of devices into RAID/etc). Each has some feature the other lacks, but ZFS is more mature.
Ultimately btrfs seems likely to replace ext4 some day, though that day could be quite a ways off. ZFS is unlikely to do so unless the license issue is overcome - sure, you can use it, but there will always be a drive to have the #1 general-purpose filesystem be one that is actually in the mainline kernel.
How is it a filesystem in the unix philsophy? It's monolithic in the worst possible way; a clumsy mess of layering violations. One analogy would be if someone said "http would be so much better if it wasn't for those pesky tcp, ip, and ethernet layers!"
I remain bitter that all of that work into advanced data protection, volume management, and efficiency features was wasted on a single filesystem instead of placed in device mapper where they belong. Then ext4 could have useful features such dedupe, load balancing, compression, etc. Hell, if proper layer constraints and software design were used FAT16 could have these features!
Shame on ZFS, shame on BTRFS, and shame on the community for supporting these abominations.
--You sound like a Luddite. Sure, in a blue-sky world ALL filesystems could have ZFS capabilities. But the ZFS implementors decided to get past all the cruft and implement it from scratch, and for the most part they've done a fantastic job. Quit complaining and being bitter and try FUNDING CODE DEVELOPMENT on the dev mapper subsystem if you want to see it happen in the next 5-10 years, or it likely never will - it's easier right now to keep those features at the FS level. LVM(+RAID) on Linux is a *horrible* hack in comparison to ZFS.
--Btrfs is playing catch-up tho; realistically I prolly wouldn't trust it entirely for the next 1.5 - 2 years, but it does have some things that ZFS lacks (more flexibility, and supposedly stable on 32-bit systems.) Once it matures it will be a fine alternative/complement to ZFS, and *damn* the layering violations - as long as it Just Works.
.
== WolfriderV6 == I'm willing to admit that *I just might* be wrong... Are you??