From: Tomasz Chmielewski <tch@virtall.com>
To: linux-btrfs@vger.kernel.org
Cc: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
Subject: Re: Kernel bug in 3.19-rc4
Date: Fri, 16 Jan 2015 10:05:35 +0900 [thread overview]
Message-ID: <672b579b39da1cc6fa5f91ba4b964731@admin.virtall.com> (raw)
> I just started some btrfs stress testing on latest linux kernel
> 3.19-rc4:
> A few hours later, filesystem stopped working - the kernel bug report
> can be found below.
Hi,
your "kernel BUG at fs/btrfs/inode.c:3142!" from 3.19-rc4 corresponds to
http://marc.info/?l=linux-btrfs&m=141903172106342&w=2 - it was "kernel
BUG at /home/apw/COD/linux/fs/btrfs/inode.c:3123!" in 3.18.1, and is
exactly the same code in both cases:
/* grab metadata reservation from transaction handle */
if (reserve) {
ret = btrfs_orphan_reserve_metadata(trans, inode);
BUG_ON(ret); /* -ENOSPC in reservation; Logic error? JDM
*/
}
--
Tomasz Chmielewski
http://www.sslrack.com
next reply other threads:[~2015-01-16 1:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 1:05 Tomasz Chmielewski [this message]
2015-01-16 7:33 ` Kernel bug in 3.19-rc4 Satoru Takeuchi
-- strict thread matches above, loose matches on Subject: below --
2015-01-15 19:46 Marcel Ritter
2015-01-16 7:43 ` Satoru Takeuchi
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=672b579b39da1cc6fa5f91ba4b964731@admin.virtall.com \
--to=tch@virtall.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=takeuchi_satoru@jp.fujitsu.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).