Comments

On Thu, 1 September 2011 11:38:39 +0530, srimugunthan dhandapani wrote:
> > Its frustrating when you ask me to take a new set of logs without> reading my previous mails.> To repeat, iam not able to reproduce the third bug. I think the first> two bugs should be reproducible at your end.
Well, so far I have basically ignored your second and third bug. As
long as the first is unresolved, I don't want to add yet more
confusion to what we already have.
> I thought that you were asking me to take the logs because you are not> able to reproduce them too.
I wanted to ask you to take the test patch, run it, see the debug
output in the kernel log and send it to me. "Take the logs" may have
been what I said, but if I did that would have been too ambiguous. A
single line of output from the debug printk would have been enough, or
maybe a pagefull. Certainly not megabytes worth.
> Out of curiosity, are you able to run bonnie successfully with logfs+nandsim?
Yes and no. I think I have to apologize for using block2mtd so far.
There shouldn't be a big difference between one mtd driver and another
wrt. logfs behaviour. Famous last words.
The problem with nandsim + logfs is the default segment size. 16k is
not enough to fit an entire journal commit into. You can try this
yourself by using "mklogfs -s14 /dev/mtd0" or "mklogfs -s15 /dev/mtd0"
in your test scripts. The first should run into the infinite loop you
experienced, while the second should work.
I'm not entirely sure what to do about this. The easiest and probably
most robust solution is to check for segment size at mount time and
fail for anything <32k.
Oh, and you might want to add the patch below.
Jörn