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 07:58:54 +0200 [thread overview]
Message-ID: <20110831055854.GA12713@logfs.org> (raw)
In-Reply-To: <CAMjNe_euj5t9+Jph0Uy-j7+SRMe1oSzihGCaiuQ1Dcd7dz6cuw@mail.gmail.com>
On Mon, 29 August 2011 15:37:09 +0530, srimugunthan dhandapani wrote:
>
> > Are you sure you have my patch applied?
> >
>
> To clarify on the bugs I reported
> 1. bonnie test( bonnie -s 20 -r 10) does not complete . It gets stuck
> at "Creating files in sequential order ..."
> (tested with nandsim, kernel 3.0.1. and 2.6.38.8; consistently
> reproducible on 2 machines.)
> The free command show that, while the bonnie test was run for half an
> hour, free space changed from 2982340 KB to 2550156 KB.
The only trouble is that no amount of bonnie output helps me to nail
this one down. What I need is the kernel output - more specificly the
output of the debug patch I sent you. Lacking that, there is nothing
I can do. Can you ensure you have my patch applied, rerun the rest
case and send me the kernel results?
Alternatively we can spend our time figuring out the differences
between your and my setup. You could run a different kernel with
different patches applied, have a different .config or a different
machine - probably all three. But my gut feeling is that it shouldn't
be too hard to fix the bug, provided you are able to run test patches
and return the results to me.
Jörn
--
Sometimes, asking the right question is already the answer.
-- Unknown
--
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 5:58 UTC|newest]
Thread overview: 21+ 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-06 14:09 ` srimugunthan dhandapani
2011-08-08 8:31 ` Jörn Engel
2011-08-08 14:44 ` srimugunthan dhandapani
2011-08-09 14:58 ` Jörn Engel
2011-08-10 11:06 ` srimugunthan dhandapani
2011-08-12 9:34 ` Jörn Engel
2011-08-12 17:26 ` srimugunthan dhandapani
2011-08-16 17:17 ` Jörn Engel
2011-08-21 21:19 ` srimugunthan dhandapani
2011-08-26 19:49 ` Jörn Engel
2011-08-29 10:07 ` srimugunthan dhandapani
2011-08-31 5:58 ` Jörn Engel [this message]
2011-08-31 7:22 ` srimugunthan dhandapani
2011-08-31 7:49 ` Jörn Engel
2011-08-31 12:49 ` srimugunthan dhandapani
2011-08-31 14:17 ` Jörn Engel
2011-09-01 6:08 ` srimugunthan dhandapani
2011-09-01 9:46 ` srimugunthan dhandapani
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=20110831055854.GA12713@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).