From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: fatal database corruption with btrfs "out of space" with ~50 GB left
Date: Thu, 15 Feb 2018 01:25:22 +0000 (UTC) [thread overview]
Message-ID: <pan$4ac0$69992a27$e9c3c183$c0ebac21@cox.net> (raw)
In-Reply-To: de1fdabb35ffe14eb92433ef444494e7@virtall.com
Tomasz Chmielewski posted on Wed, 14 Feb 2018 23:19:20 +0900 as excerpted:
> 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!)".
Ouch!
> Running btrfs RAID-1 with kernel 4.14.
Kernel 4.14... quite current... good. But 4.14.0 first release, 4.14.x
current stable, or somewhere (where?) in between?
And please post the output of btrfs fi usage for that filesystem.
Without that (or fi sh and fi df, the pre-usage method of getting nearly
the same info), it's hard to say where or what the problem was.
Meanwhile, FWIW there was a recent metadata over-reserve bug that should
be fixed in 4.15 and the latest 4.14 stable, but IDR whether it affected
4.14.0 original or only the 4.13 series and early 4.14-rcs and was fixed
by 4.14.0. The bug seemed to trigger most frequently when doing balances
or other major writes to the filesystem, on middle to large sized
filesystems. (My all under quarter-TB each btrfs didn't appear to be
affected.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2018-02-15 1: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 [this message]
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
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='pan$4ac0$69992a27$e9c3c183$c0ebac21@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/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).