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.
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)
You are not the only person who have reported data loss on btrfs. Normally I wouldn't worry about Linux filesystems (even ext4 became rock solid after a while.) However, I worry about what I hear from people who use btrfs.
One concern is that a filesystem can't check for bit rot by itself. True bit rot checking requires at least some working with the LVM layer to check CRCs, find a damaged sector and fix it. I've read that btrfs can catch some bitrot issues, (and please correct me if wrong), but it can't catch/correct anywhere near as much as ZFS or Storage Spaces + ReFS can. btrfs also uses a 32 bit CRC, rather than a 64 bit one.
I'm hoping that Facebook's coders can find the issues with btrfs and squash them. There are not many companies with the sheer server use of FB, and if they can get it working solidly, btrfs should be more than ready for prime time for everyone else.
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.
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...