linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Niraj Kulkarni <kulkarniniraj14@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Help required for Debugging JBD
Date: Wed, 22 Jun 2011 09:43:52 +0300	[thread overview]
Message-ID: <BANLkTimhig+_Lb52KMcRyk5S4YQcdYozVg@mail.gmail.com> (raw)
In-Reply-To: <4E00CC36.80707@gmail.com>

On Tue, Jun 21, 2011 at 7:52 PM, Niraj Kulkarni
<kulkarniniraj14@gmail.com> wrote:
> Hi all,
>        I have modified my JBD (no change to Ext3) to support
> Transactional-Flash. For that I require only to collect metadata and data
> blocks and send them simultaneously (no transaction record, revoke record
> etc).

It's hard to help without knowing what your patches do in more details.
Could you post the patches or give a more detailed description of how they
work?
For example, how do you collect data blocks without them being already
written? or is this not a requirement for your use case?

>       The problem is, though it works well for small number of operations,
> the kernel completely hangs when I run any benchmark (like blogbench or
> postmark) over them. The bad thing is that there is no trace left
> afterwards, ie logs don't contain any message since the operation was
> started, kernel OOPS are not shown, no faults are shown, no panic is shown
> even though I have enabled panic on hard/soft lockup. I have to hard reboot
> machine each time.

Did you try alt+sysrq+w to dump waiting tasks?

>        So essentially, I am totally clueless about the point  at which it is
> crashing or reason behind it. There is a small possibility that bug may be
> in modified MTD layer (which I've written myself), but since I have run
> unmodified Ext3 on that MTD layer without any bug, the chance of buggy MTD
> layer appears very slim.
>
> Any help in greatly appreciated.
>
> Niraj
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-06-22  6:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21 16:52 Help required for Debugging JBD Niraj Kulkarni
2011-06-22  6:43 ` Amir Goldstein [this message]
2011-06-22 18:27   ` Niraj Kulkarni
2011-06-22 19:29     ` Amir Goldstein

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=BANLkTimhig+_Lb52KMcRyk5S4YQcdYozVg@mail.gmail.com \
    --to=amir73il@gmail.com \
    --cc=kulkarniniraj14@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    /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).