From: Erkki Seppala <flux-btrfs@inside.org>
To: linux-btrfs@vger.kernel.org
Subject: BTRFS BUG at insert_inline_extent_backref+0xe3/0xf0 while rebalancing
Date: Thu, 22 Oct 2015 08:32:40 +0300 [thread overview]
Message-ID: <m49lhavbh8n.fsf@coffee.modeemi.fi> (raw)
Hello,
Recently I added daily rebalancing to my cron.d (after finding myself in
the no-space-situation), and not long after that, I found my PC had
crashed over night. Having no sign in the logs anywhere (not even over
network even though there should be) I had nothing to go on, but this
night it crashed again after starting the rebalance, and this time there
was some information on the kernel log.
Kernel version: 4.2.3 (package linux-image-4.2.0-1-amd64 version 4.2.3-1
from Debian Unstable)
The dump is available at:
http://www.modeemi.fi/~flux/btrfs/btrfs-BUG-2015-10-55.txt
The log is available as well (stripped some unrelated USB- and firewall
logging, showing that last evening there was some kernel task hung for
120 seconds; but it's in another btrfs filesystem and is another story):
http://www.modeemi.fi/~flux/btrfs/btrfs-2015-10-55.txt
I'm not quite sure which of the btrfs balance commands caused the
issue. But there is my script:
#!/bin/sh
fs="$1"
if [ -z "$fs" ]; then
echo usage: btrfs-balance / 0 1 5 10 20 50
exit 1
fi
fs="$1"
shift
for usage in d m; do for a in "$@"; do date; /bin/btrfs balance start
"$fs" -v -${usage}usage=$a; done; done
And it was started at 07:30 with:
/usr/local/sbin/btrfs-balance / 0 1 2 5 10 20 30 50 70
I should add that the filesystem in question is backed by MD RAID10 and
that is backed by four SSDs, so it's reasonably fast in IO, if that
affects anything. There should have been no much competing IO at the
time of the occurrence.
Before Duncan asks ;-), I only have a moderate number of subvolumes and
snapshots, ie. one subvolume for each of /, /var/log/journal and /home,
24 snapshots of / and /home plus <10 snapshots of /.
Before that balance there was another balance on a another BTRFS RAID10,
but given the time stamp I think I can easily say it wasn't the cause.
I don't really have other 'solutions' than disabling the rebalancing for
the time being, and only use it as-needed as I had earlier done..
Cheers,
--
_____________________________________________________________________
/ __// /__ ____ __ http://www.modeemi.fi/~flux/\ \
/ /_ / // // /\ \/ / \ /
/_/ /_/ \___/ /_/\_\@modeemi.fi \/
next reply other threads:[~2015-10-22 5:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 5:32 Erkki Seppala [this message]
2015-10-22 8:53 ` BTRFS BUG at insert_inline_extent_backref+0xe3/0xf0 while rebalancing Filipe Manana
2015-10-22 10:06 ` Stéphane Lesimple
2015-10-22 16:55 ` Erkki Seppala
2015-10-30 8:57 ` Erkki Seppala
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=m49lhavbh8n.fsf@coffee.modeemi.fi \
--to=flux-btrfs@inside.org \
--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