From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: 3.14.18 btrfs_set_item_key_safe BUG
Date: Tue, 16 Sep 2014 10:21:04 +0000 (UTC) [thread overview]
Message-ID: <pan.2014.09.16.10.21.04@googlemail.com> (raw)
In-Reply-To: pan.2014.09.16.07.38.22@googlemail.com
On Tue, 16 Sep 2014 07:38:22 +0000, Holger Hoffstätte wrote:
> On Tue, 16 Sep 2014 12:33:09 +0800, Daniel J Blueman wrote:
>
>> kernel BUG at /home/apw/COD/linux/fs/btrfs/ctree.c:3215!
>
> This matches exactly the description mentioned just recently:
> http://article.gmane.org/gmane.comp.file-systems.btrfs/38340
>
> (not in that posting, but in the patch description).
>
> You seem to be running a custom kernel, so try if that patch
> helps. Also try nuking the free space cache when you have it
> applied.
In order to apply that patch you will first need:
"Btrfs: don't insert useless holes when punching beyond the inode's size"
https://git.kernel.org/cgit/linux/kernel/git/mason/linux-btrfs.git/commit/fs/btrfs?h=for-linus&id=12870f1c9b2de7d475d22e73fd7db1b418599725
With that it applies cleanly to 3.14.18/19.
-h
prev parent reply other threads:[~2014-09-16 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 4:33 3.14.18 btrfs_set_item_key_safe BUG Daniel J Blueman
2014-09-16 7:38 ` Holger Hoffstätte
2014-09-16 10:21 ` Holger Hoffstätte [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=pan.2014.09.16.10.21.04@googlemail.com \
--to=holger.hoffstaette@googlemail.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;
as well as URLs for NNTP newsgroup(s).