From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?B?SsO2cm4=?= Engel Subject: Re: logfs unmount bug Date: Tue, 16 Aug 2011 19:17:07 +0200 Message-ID: <20110816171707.GU26160@logfs.org> References: <20110805160325.GM26160@logfs.org> <20110808083107.GN26160@logfs.org> <20110809145812.GR26160@logfs.org> <20110812093429.GS26160@logfs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org To: srimugunthan dhandapani Return-path: Received: from [85.183.114.52] ([85.183.114.52]:39915 "EHLO Dublin.logfs.org" rhost-flags-FAIL-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1751892Ab1HPRQb (ORCPT ); Tue, 16 Aug 2011 13:16:31 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, 12 August 2011 22:56:02 +0530, srimugunthan dhandapani wrote: >=20 > > I wouldn't suspect any code changes to cause the different behaviou= r. > > Kernel config and test machine (memsize, etc.) would be more likely > > candidates. =C2=A0So if you could try the patch and send me the out= put, > > that would be useful. >=20 > I tried your patches and I also tried on official kernel release 3.0.= 1. > I have shared the bonnie output and logs in the below link: >=20 > https://docs.google.com/leaf?id=3D0BycgLWCW61phNjY0ZDg4ZjUtYzAyMy00YT= gwLWFlMmItNjlmZWIzMWFlNGUy&hl=3Den_US Are you sure you tried the first patch? When I grep for "logfs_invalidatepage", I only find the oopses, not my debug output. > I did all my tests with nandsim. Are there any problems using logfs > with nandsim? Shouldn't be, unless nandsim is corrupting memory in a peculiar and reproduceable way on your system. J=C3=B6rn --=20 Unless something dramatically changes, by 2015 we'll be largely wondering what all the fuss surrounding Linux was really about. -- Rob Enderle -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [85.183.114.52] (helo=Dublin.logfs.org) by canuck.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1QtNFg-00080h-UP for linux-mtd@lists.infradead.org; Tue, 16 Aug 2011 17:16:33 +0000 Date: Tue, 16 Aug 2011 19:17:07 +0200 From: =?utf-8?B?SsO2cm4=?= Engel To: srimugunthan dhandapani Subject: Re: logfs unmount bug Message-ID: <20110816171707.GU26160@logfs.org> References: <20110805160325.GM26160@logfs.org> <20110808083107.GN26160@logfs.org> <20110809145812.GR26160@logfs.org> <20110812093429.GS26160@logfs.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Cc: linux-fsdevel@vger.kernel.org, linux-mtd@lists.infradead.org List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, 12 August 2011 22:56:02 +0530, srimugunthan dhandapani wrote: > > > I wouldn't suspect any code changes to cause the different behaviour. > > Kernel config and test machine (memsize, etc.) would be more likely > > candidates.  So if you could try the patch and send me the output, > > that would be useful. > > I tried your patches and I also tried on official kernel release 3.0.1. > I have shared the bonnie output and logs in the below link: > > https://docs.google.com/leaf?id=0BycgLWCW61phNjY0ZDg4ZjUtYzAyMy00YTgwLWFlMmItNjlmZWIzMWFlNGUy&hl=en_US Are you sure you tried the first patch? When I grep for "logfs_invalidatepage", I only find the oopses, not my debug output. > I did all my tests with nandsim. Are there any problems using logfs > with nandsim? Shouldn't be, unless nandsim is corrupting memory in a peculiar and reproduceable way on your system. Jörn -- Unless something dramatically changes, by 2015 we'll be largely wondering what all the fuss surrounding Linux was really about. -- Rob Enderle