linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: Tomasz Chmielewski <tch@virtall.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: fatal database corruption with btrfs "out of space" with ~50 GB left
Date: Mon, 19 Feb 2018 12:29:59 +0800	[thread overview]
Message-ID: <d8289a56-5874-dfe9-60fd-72b3c06b1664@oracle.com> (raw)
In-Reply-To: <de1fdabb35ffe14eb92433ef444494e7@virtall.com>



On 02/14/2018 10:19 PM, Tomasz Chmielewski wrote:
> 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!)".

  Thanks for reporting.

> Running btrfs RAID-1 with kernel 4.14.

  Can you pls let us know..
  1. What tool cli/reported/identified that data is corrupted?
  2. Disk error stat using.. btrfs dev stat <mnt>
     (dev stat is stored on disk)
  3. Wheather the disk was mounted as degraded any time before?

Thanks, Anand

  parent reply	other threads:[~2018-02-19  4:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 14:19 fatal database corruption with btrfs "out of space" with ~50 GB left Tomasz Chmielewski
2018-02-15  1:25 ` Duncan
2018-02-15  1:47 ` Qu Wenruo
2018-02-15  4:19   ` Tomasz Chmielewski
2018-02-15  4:32     ` Qu Wenruo
2018-02-15  7:02       ` Tomasz Chmielewski
2018-02-15  7:17         ` Tomasz Chmielewski
2018-02-15  9:06           ` Nikolay Borisov
2018-02-15  7:38         ` Qu Wenruo
2018-02-15  7:50         ` Duncan
2018-02-19  4:29 ` Anand Jain [this message]
2018-02-19  8:30   ` Tomasz Chmielewski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d8289a56-5874-dfe9-60fd-72b3c06b1664@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=tch@virtall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).