From: Govindarajulu Varadarajan <_govind@gmx.com>
To: Josef Bacik <jbacik@fb.com>
Cc: Govindarajulu Varadarajan <_govind@gmx.com>,
linux-btrfs@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-kernel@vger.kernel.org, clm@fb.com, dsterba@suse.cz
Subject: Re: btrfs: kernel BUG at mm/page-writeback.c:2286!
Date: Thu, 21 May 2015 14:09:24 +0530 (IST) [thread overview]
Message-ID: <alpine.LNX.2.03.1505211407010.19285@ws.cisco> (raw)
In-Reply-To: <555B3B5D.7040601@fb.com>
On Tue, 19 May 2015, Josef Bacik wrote:
> On 05/19/2015 03:55 AM, Govindarajulu Varadarajan wrote:
>> Hi all
>>
>> I am seeing the following crash on my btrfs filesystem with nfs export.
>> If I disable the nfs share and reboot, I do not hit the crash. Look like
>> the crash happens on btrfs with nfs export.
>>
>> Is this a known issue? Has anyone else faced this? Let me know if you
>> need more
>> information.
>>
>
> Somebody else is unlocking the page while we have it locked (by somebody else
> I mean somebody other than in this particular code path, so could totally
> still be us, it's just not obvious.) What are your mount options? Are you
> capable of building your own kernel? A git bisect would be good to try and
> find where the problem was introduced, seems like it's easy to reproduce.
> I'll look through our recent commits and see if anything pops out. Thanks,
>
Yes, I can do git bisect. But, now that I have deleted the file with csum error
I do not see the crash any more. Sorry.
Is there any was to introduce
"BTRFS info (device sdf): csum failed ino 1154 extent 4434247680 csum 1388825687 wanted 0 mirror 0"?
next prev parent reply other threads:[~2015-05-21 8:39 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 [this message]
2015-05-19 13:43 ` Chris Mason
2015-05-19 13:54 ` Piotr Szymaniak
2015-05-19 14:44 ` Chris Mason
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=alpine.LNX.2.03.1505211407010.19285@ws.cisco \
--to=_govind@gmx.com \
--cc=clm@fb.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 \
/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