From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?B?SsO2cm4=?= Engel Subject: Re: logfs unmount bug Date: Wed, 31 Aug 2011 09:49:02 +0200 Message-ID: <20110831074902.GA26382@logfs.org> References: <20110809145812.GR26160@logfs.org> <20110812093429.GS26160@logfs.org> <20110816171707.GU26160@logfs.org> <20110826194910.GE22411@logfs.org> <20110831055854.GA12713@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]:52432 "EHLO Dublin.logfs.org" rhost-flags-FAIL-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1754615Ab1HaHsV (ORCPT ); Wed, 31 Aug 2011 03:48:21 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, 31 August 2011 12:52:54 +0530, srimugunthan dhandapani wrote: > On Wed, Aug 31, 2011 at 11:28 AM, J=C3=B6rn Engel w= rote: >=20 > > I can do. =C2=A0Can you ensure you have my patch applied, rerun the= rest > > case and send me the kernel results? >=20 > I applied your patch1 and the bonnie output is the same(stuck at > "Creating files in sequential order ..."). The kernel is from your > git directory(http://git.kernel.org/?p=3Dlinux/kernel/git/joern/logfs= =2Egit;a=3Dsummary) > I am pretty sure i applied the patch. The git diff output is below[1] >=20 > The kernel log is at > https://docs.google.com/leaf?id=3D0BycgLWCW61phNjY0ZDg4ZjUtYzAyMy00Y= TgwLWFlMmItNjlmZWIzMWFlNGUy&hl=3Den_US 600M. And starting at line 34285 or about 0% in, the output mutates to something like the below. Not very useful. :( Aug 31 12:28:06 mll kernel: [ 991.561293] logfs_write_obj_alia 8,, 83,= (3f(320(#2 #s #es sesaseiaslialilialilialialialialialialialialialialial= ialialilialialialilialialialililialialialilialialialilililialialialiali= alilialialiallialilialialialiaali_alj_abjo_ws_fsgfogflo lo] l4] 7581586= 156.561.591.9 9 [ >[7>[<7 Aug 31 12:28:06 mll kernel: <7 Aug 31 12:28:07 mll kernel: last message repeated 4 times Aug 31 12:28:06 mll kernel: < Aug 31 12:28:06 mll kernel: <7 Aug 31 12:28:06 mll kernel: <7 Aug 31 12:28:06 mll kernel: < Aug 31 12:28:06 mll kernel: < Aug 31 12:28:06 mll kernel: <7 Aug 31 12:28:06 mll kernel: <7 Aug 31 12:28:06 mll kernel: < Can you set LOGFS_DEBUG to 0, both to cut down the noise and in the hope that the log output doesn't get corrupted like this again? > While i still have your attention, i would like to point out at max > writepage size restriction in logfs. Currently logfs has a max > writepage size as 4K. Currently, large page nand flashes and MLC nand > come in 8K page sizes. As the usecase for logfs is large nand > flashes(mostly with parallel and DMA write capabilities), it may be > essential to remove the 4K write page size restriction. > I was only able to change the logfs-tools for >4K writepage size. If > you send a patch, that makes logfs useable for writepagesize >4K, i > can try on real hardware, instead of nandsim and give you the results > :-) That sure sounds useful. I'll have a look... J=C3=B6rn --=20 "Security vulnerabilities are here to stay." -- Scott Culp, Manager of the Microsoft Security Response Center, 2001 -- 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