From: Chris Mason <clm@fb.com>
To: Piotr Szymaniak <szarpaj@grubelek.pl>
Cc: Govindarajulu Varadarajan <_govind@gmx.com>,
<linux-btrfs@vger.kernel.org>, <linux-nfs@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <jbacik@fb.com>,
<dsterba@suse.cz>
Subject: Re: btrfs: kernel BUG at mm/page-writeback.c:2286!
Date: Tue, 19 May 2015 10:44:30 -0400 [thread overview]
Message-ID: <555B4C4E.2020403@fb.com> (raw)
In-Reply-To: <20150519135416.GO2539@wloczykij>
On 05/19/2015 09:54 AM, Piotr Szymaniak wrote:
> On Tue, May 19, 2015 at 09:43:10AM -0400, Chris Mason wrote:
>> On 05/19/2015 03:55 AM, Govindarajulu Varadarajan wrote:
>>> 2286--->BUG_ON(!PageLocked(page));
>>>
>>> [ 166.769868] BTRFS info (device sdf): no csum found for inode 1154
>>> start 43192320
>>> [ 166.774334] BTRFS info (device sdf): csum failed ino 1154 extent
>>> 4434247680 csum 1388825687 wanted 0 mirror 0
>>
>>
>> Josef and I both missed this the first time you pasted it, but the
>> unlocked page is almost certainly related to this csum error. While
>> we're looking at things can you please scrub?
Josef and I just read through all of this, and I'm not finding a way to
connect the crc error to the BUG_ON. Do all kernels crash like this, or
was it just 4.1-rc?
-chris
next prev parent reply other threads:[~2015-05-19 14:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 7:55 btrfs: kernel BUG at mm/page-writeback.c:2286! Govindarajulu Varadarajan
2015-05-19 13:00 ` Duncan
2015-05-19 13:32 ` Josef Bacik
2015-05-21 8:39 ` Govindarajulu Varadarajan
2015-05-19 13:43 ` Chris Mason
2015-05-19 13:54 ` Piotr Szymaniak
2015-05-19 14:44 ` Chris Mason [this message]
2015-05-21 8:36 ` Govindarajulu Varadarajan
2015-05-21 8:33 ` Govindarajulu Varadarajan
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=555B4C4E.2020403@fb.com \
--to=clm@fb.com \
--cc=_govind@gmx.com \
--cc=dsterba@suse.cz \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=szarpaj@grubelek.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.