From: "Jörn Engel" <joern@logfs.org>
To: srimugunthan dhandapani <srimugunthan.dhandapani@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: logfs unmount bug
Date: Wed, 31 Aug 2011 16:17:31 +0200 [thread overview]
Message-ID: <20110831141731.GA29862@logfs.org> (raw)
In-Reply-To: <CAMjNe_csYHWCRFXt6sW1FpMaS_RFGLM6z1ML6_-3xb-5x7DZtg@mail.gmail.com>
On Wed, 31 August 2011 18:19:30 +0530, srimugunthan dhandapani wrote:
> On Wed, Aug 31, 2011 at 1:19 PM, Jörn Engel <joern@logfs.org> 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
WARNING: multiple messages have this Message-ID (diff)
From: "Jörn Engel" <joern@logfs.org>
To: srimugunthan dhandapani <srimugunthan.dhandapani@gmail.com>
Cc: linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org
Subject: Re: logfs unmount bug
Date: Wed, 31 Aug 2011 16:17:31 +0200 [thread overview]
Message-ID: <20110831141731.GA29862@logfs.org> (raw)
In-Reply-To: <CAMjNe_csYHWCRFXt6sW1FpMaS_RFGLM6z1ML6_-3xb-5x7DZtg@mail.gmail.com>
On Wed, 31 August 2011 18:19:30 +0530, srimugunthan dhandapani wrote:
> On Wed, Aug 31, 2011 at 1:19 PM, Jörn Engel <joern@logfs.org> 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
--
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
next prev parent reply other threads:[~2011-08-31 14:16 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 19:35 logfs unmount bug srimugunthan dhandapani
2011-08-05 16:03 ` Jörn Engel
2011-08-05 16:03 ` Jörn Engel
2011-08-06 14:09 ` srimugunthan dhandapani
2011-08-06 14:09 ` srimugunthan dhandapani
2011-08-08 8:31 ` Jörn Engel
2011-08-08 8:31 ` Jörn Engel
2011-08-08 14:44 ` srimugunthan dhandapani
2011-08-08 14:44 ` srimugunthan dhandapani
2011-08-09 14:58 ` Jörn Engel
2011-08-09 14:58 ` Jörn Engel
2011-08-10 11:06 ` srimugunthan dhandapani
2011-08-10 11:06 ` srimugunthan dhandapani
2011-08-12 9:34 ` Jörn Engel
2011-08-12 9:34 ` Jörn Engel
2011-08-12 17:26 ` srimugunthan dhandapani
2011-08-12 17:26 ` srimugunthan dhandapani
2011-08-16 17:17 ` Jörn Engel
2011-08-16 17:17 ` Jörn Engel
2011-08-21 21:19 ` srimugunthan dhandapani
2011-08-21 21:19 ` srimugunthan dhandapani
2011-08-26 19:49 ` Jörn Engel
2011-08-26 19:49 ` Jörn Engel
2011-08-29 10:07 ` srimugunthan dhandapani
2011-08-29 10:07 ` srimugunthan dhandapani
2011-08-31 5:58 ` Jörn Engel
2011-08-31 5:58 ` Jörn Engel
2011-08-31 7:22 ` srimugunthan dhandapani
2011-08-31 7:22 ` srimugunthan dhandapani
2011-08-31 7:49 ` Jörn Engel
2011-08-31 7:49 ` Jörn Engel
2011-08-31 12:49 ` srimugunthan dhandapani
2011-08-31 12:49 ` srimugunthan dhandapani
2011-08-31 14:17 ` Jörn Engel [this message]
2011-08-31 14:17 ` Jörn Engel
2011-09-01 6:08 ` srimugunthan dhandapani
2011-09-01 6:08 ` srimugunthan dhandapani
2011-09-01 9:46 ` srimugunthan dhandapani
2011-09-01 9:46 ` srimugunthan dhandapani
2011-09-01 21:34 ` Jörn Engel
2011-09-01 21:34 ` Jörn Engel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110831141731.GA29862@logfs.org \
--to=joern@logfs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=srimugunthan.dhandapani@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.