Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755841AbbEUIhJ (ORCPT ); Thu, 21 May 2015 04:37:09 -0400 Received: from mout.gmx.net ([212.227.15.18]:52956 "EHLO mout.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753181AbbEUIhF (ORCPT ); Thu, 21 May 2015 04:37:05 -0400 Date: Thu, 21 May 2015 14:06:48 +0530 (IST) From: Govindarajulu Varadarajan <_govind@gmx.com> X-X-Sender: gvaradar@ws.cisco To: Chris Mason cc: Piotr Szymaniak , 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! In-Reply-To: <555B4C4E.2020403@fb.com> Message-ID: References: <555B3DEE.1000900@fb.com> <20150519135416.GO2539@wloczykij> <555B4C4E.2020403@fb.com> User-Agent: Alpine 2.03 (LNX 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Provags-ID: V03:K0:TtRC2IPXS+jzm306jY34FlZ1MxKGKGKLed5xhpuktIgqSGePGMI Stl0AH6NBbSxgOcI0/I06xQNCQHtWh3EqQI0yd/C3Gta/H37XMdhyycOJLMvyzNGSO3h0DT Sr1Ps7j3KuzglVGXI0j82v+/T9UTt7Smla0dkePX4Osp1p0ouQQQ0dvoOEHzK6PXYvRagPK LlmquqZrUmFEP3BSRXG4A== X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1322 Lines: 31 On Tue, 19 May 2015, Chris Mason wrote: > 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? > The csum error was for one of the files. Scrub did not fix it. When I run Scrub it shows 0 error. So I deleted the file. I do no see the crash now. Crash did not happen on 3.18 kernel. I first faced this problem in 3.19. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/