From: Omar Sandoval <osandov@osandov.com>
To: Kai Krakow <hurikhan77@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Hard crash on 4.9.5
Date: Mon, 13 Mar 2017 15:19:02 -0700 [thread overview]
Message-ID: <20170313221902.GA2352@vader.DHCP.thefacebook.com> (raw)
In-Reply-To: <20170313225829.01c06724@jupiter.sol.kaishome.de>
On Mon, Mar 13, 2017 at 10:58:29PM +0100, Kai Krakow wrote:
> Am Sat, 28 Jan 2017 15:50:38 -0500
> schrieb Matt McKinnon <matt@techsquare.com>:
>
> > This same file system (which crashed again with the same errors) is
> > also giving this output during a metadata or data balance:
>
> This looks somewhat familiar to the err=-17 that I am experiencing when
> using VirtualBox image on btrfs in CoW mode (compress=lzo).
>
> During IO intensive workloads, it results in "object already exists,
> err -17" (or similar, someone else also experienced it through another
> workload). The resulting btrfs check show the same errors, giving
> inodes without csum.
>
> Trying to continue using this file system in successive boots usually
> results in boot freezes or complete unmountable filesystem, broken
> beyond repair.
>
> I'm feeling that using the bfq elevator usually enables me to trigger
> this bug also without using VirtualBox, i.e. during normal system
> usage, and mostly during boot when IO load is very high. So I also
> stopped using bfq although it was giving me a much superior
> interactivity.
>
> Marking vbox images nocow and using standard elevators (cfq, deadline)
> exposes no such problems so far - even during excessive IO loads.
>
> EOM
This sounds similar to a bug I fixed here:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8e2bd3b7fac91b79a6115fd1511ca20b2a09696d
That change is in v4.10. If you're not already running a kernel version
with that fix, could you check if that solves it?
prev parent reply other threads:[~2017-03-13 22:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 20:03 Hard crash on 4.9.5 Matt McKinnon
2017-01-23 20:27 ` Hans van Kranenburg
2017-01-23 20:33 ` Hans van Kranenburg
2017-01-25 16:20 ` Liu Bo
2017-01-25 21:06 ` Liu Bo
2017-01-28 20:50 ` Matt McKinnon
2017-03-13 21:58 ` Kai Krakow
2017-03-13 22:19 ` Omar Sandoval [this message]
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=20170313221902.GA2352@vader.DHCP.thefacebook.com \
--to=osandov@osandov.com \
--cc=hurikhan77@gmail.com \
--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