From mboxrd@z Thu Jan 1 00:00:00 1970 From: srimugunthan dhandapani Subject: Re: logfs unmount bug Date: Wed, 31 Aug 2011 18:19:30 +0530 Message-ID: References: <20110809145812.GR26160@logfs.org> <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=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org To: =?ISO-8859-1?Q?J=F6rn_Engel?= Return-path: Received: from mail-yi0-f46.google.com ([209.85.218.46]:57449 "EHLO mail-yi0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755510Ab1HaMtb convert rfc822-to-8bit (ORCPT ); Wed, 31 Aug 2011 08:49:31 -0400 Received: by yie30 with SMTP id 30so533405yie.19 for ; Wed, 31 Aug 2011 05:49:31 -0700 (PDT) In-Reply-To: <20110831074902.GA26382@logfs.org> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, Aug 31, 2011 at 1:19 PM, J=F6rn 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= =3D0. I produced the log with LOGFS_DEBUG=3D0xDFF, (without LOGFS_DEBUG_ALIAS= ES) Its a 60MB log file "kern_LOGFS_DEBUG=3D0xDFF.log" shared in the follow= ing link: https://docs.google.com/leaf?id=3D0BycgLWCW61phNjY0ZDg4ZjUtYzAyMy00YTgw= LWFlMmItNjlmZWIzMWFlNGUy&hl=3Den_US Thanks, mugunthan -- 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