From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.virtall.com ([46.4.129.203]:48902 "EHLO mail.virtall.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030429AbeBNOZ3 (ORCPT ); Wed, 14 Feb 2018 09:25:29 -0500 Received: from mail.virtall.com (localhost [127.0.0.1]) by mail.virtall.com (Postfix) with ESMTP id 3806A1E1145D for ; Wed, 14 Feb 2018 14:19:22 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) (Authenticated sender: tch@virtall.com) by mail.virtall.com (Postfix) with ESMTPSA for ; Wed, 14 Feb 2018 14:19:22 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Date: Wed, 14 Feb 2018 23:19:20 +0900 From: Tomasz Chmielewski To: Btrfs BTRFS Subject: fatal database corruption with btrfs "out of space" with ~50 GB left Message-ID: Sender: linux-btrfs-owner@vger.kernel.org List-ID: Just FYI, how dangerous running btrfs can be - we had a fatal, unrecoverable MySQL corruption when btrfs decided to do one of these "I have ~50 GB left, so let's do out of space (and corrupt some files at the same time, ha ha!)". Running btrfs RAID-1 with kernel 4.14. Tomasz Chmielewski https://lxadm.com