btrfs Meltdown | LUP 87 | Jupiter Broadcasting

btrfs Meltdown | LUP 87

Posted on: April 7, 2015

Posted in: Featured, LINUX Unplugged, Video

After yet another gotcha takes down a critical Linux workstation, is it officially time to consider avoiding btrfs when it matters?

Plus what happened to the Evolve OS project & why they are now called Solus.

Thanks to:

Get Paid to Write for DigitalOcean

Direct Download:

RSS Feeds:

Become a supporter on Patreon:

Show Notes:

Pre-Show:

The best HDMI operating system sticks | ZDNet

Catch Up:

CoreOS today announced a new $12 million round of funding as well as a new product called Tectonic that is based on the Google Kubernetes open-source project for container orchestration.

Kubernetes by Google

DigitalOcean

DigitalOcean: SSD Cloud Server, VPS Server, Simple Cloud Hosting

Dell XPS 13 (2015) developer edition now available – runs Ubuntu 14.04 SP1

XPS 13 Dev Edition with Ubuntu 14.04

LinuxFest Northwest 2015

Bellingham, WA • April 25th & 26th

Holy cookies I did it..

I created a Jupiter Broadcasting Meetup group. I was inspired by the idea of how nice it would be to have a rough idea of how many folks will be making it out to LFNW. Just to help with planning.

tl;dr

Going to LFNW 2015: LFNW 2015 – Jupiter Broadcasting Meetup please register, thaaaank you.
Want to attend future JB events in Seattle, or your area? Join our group: Jupiter Broadcasting Meetup (Seattle, WA) – Meetup
Contact | LinuxFest Northwest 2015

TING

Ting – mobile that makes sense

The Death of Chris’ #1 Rig

Death of my #1 Rig Captured

Another btrfs snafu… glad I am sitting this one out

Stable kernel version 3.19.1+ can cause a deadlock at mount time
workaround: boot with older kernel, or run btrfs-zero-log to clear the log (beware of the consequences)
fix: scheduled for 3.19.4, or apply 9c4f61f01d269815bb7c37.
also affected: 3.14.35+, 3.18.9+
Versions from 3.15 up to 3.16.1 suffer from a deadlock that was observed during heavy rsync workloads with compression on, it’s recommended to use 3.16.2 and newer

Fedora Server 22 Is Using The XFS File-System By Default

The server edition of Fedora 22 is using the XFS file-system by default rather than EXT4.
Using the XFS file-system as the default within an LVM has been part of the Fedora Server technical spec while with Fedora 22 it’s finally happened. The default layout for Fedora Server 22 installations is using XFS atop LVM while /boot is outside the LVM setup.