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 1Qylb2-0000A8-J7 for linux-mtd@lists.infradead.org; Wed, 31 Aug 2011 14:16:53 +0000 Date: Wed, 31 Aug 2011 16:17:31 +0200 From: =?utf-8?B?SsO2cm4=?= Engel To: srimugunthan dhandapani Subject: Re: logfs unmount bug Message-ID: <20110831141731.GA29862@logfs.org> References: <20110812093429.GS26160@logfs.org> <20110816171707.GU26160@logfs.org> <20110826194910.GE22411@logfs.org> <20110831055854.GA12713@logfs.org> <20110831074902.GA26382@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 Wed, 31 August 2011 18:19:30 +0530, srimugunthan dhandapani wrote: > On Wed, Aug 31, 2011 at 1:19 PM, Jörn Engel wrote: > > > 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? > > It doesn't crash, so nothing much is printed in kern.log if LOGFS_DEBUG=0. Ok. So for those of us who are a bit slow (me), you say that you cannot reproduce the bug with LOGFS_DEBUG=0. In order to reproduce it, you have to set LOGFS_DEBUG=LOGFS_DEBUG_ALL or some such. Is that right? > I produced the log with LOGFS_DEBUG=0xDFF, (without LOGFS_DEBUG_ALIASES) > Its a 60MB log file "kern_LOGFS_DEBUG=0xDFF.log" shared in the following link: > > https://docs.google.com/leaf?id=0BycgLWCW61phNjY0ZDg4ZjUtYzAyMy00YTgwLWFlMmItNjlmZWIzMWFlNGUy&hl=en_US LOGFS_DEBUG=0xDFF is equivalent to LOGFS_DEBUG=LOGFS_DEBUG_ALL - the unset bits aren't used anyway. Which leaves me utterly confused. Were you unable to reproduce, but you sent me the log anyway? Jörn -- The grand essentials of happiness are: something to do, something to love, and something to hope for. -- Allan K. Chalmers 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 16:17:31 +0200 Message-ID: <20110831141731.GA29862@logfs.org> References: <20110812093429.GS26160@logfs.org> <20110816171707.GU26160@logfs.org> <20110826194910.GE22411@logfs.org> <20110831055854.GA12713@logfs.org> <20110831074902.GA26382@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]:59157 "EHLO Dublin.logfs.org" rhost-flags-FAIL-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1752129Ab1HaOQy (ORCPT ); Wed, 31 Aug 2011 10:16:54 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, 31 August 2011 18:19:30 +0530, srimugunthan dhandapani wrote: > On Wed, Aug 31, 2011 at 1:19 PM, J=C3=B6rn Engel wr= ote: >=20 > > 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? >=20 > It doesn't crash, so nothing much is printed in kern.log if LOGFS_DEB= UG=3D0. Ok. So for those of us who are a bit slow (me), you say that you cannot reproduce the bug with LOGFS_DEBUG=3D0. In order to reproduce it, you have to set LOGFS_DEBUG=3DLOGFS_DEBUG_ALL or some such. Is tha= t right? > I produced the log with LOGFS_DEBUG=3D0xDFF, (without LOGFS_DEBUG_ALI= ASES) > Its a 60MB log file "kern_LOGFS_DEBUG=3D0xDFF.log" shared in the foll= owing link: >=20 > https://docs.google.com/leaf?id=3D0BycgLWCW61phNjY0ZDg4ZjUtYzAyMy00YT= gwLWFlMmItNjlmZWIzMWFlNGUy&hl=3Den_US LOGFS_DEBUG=3D0xDFF is equivalent to LOGFS_DEBUG=3DLOGFS_DEBUG_ALL - th= e unset bits aren't used anyway. Which leaves me utterly confused. Were you unable to reproduce, but you sent me the log anyway? J=C3=B6rn --=20 The grand essentials of happiness are: something to do, something to love, and something to hope for. -- Allan K. Chalmers -- 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