linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Graham Murray <graham@gmurray.org.uk>
Cc: linux-ext4@vger.kernel.org
Subject: Re: All processes accessing etx4 partition stuck in 'D' state
Date: Mon, 19 Jan 2009 07:43:05 -0500	[thread overview]
Message-ID: <20090119124305.GB7598@mit.edu> (raw)
In-Reply-To: <87ljt7zt9q.fsf@newton.gmurray.org.uk>

On Mon, Jan 19, 2009 at 06:47:45AM +0000, Graham Murray wrote:
> I do not know if this is ext4 related or not, so my apologies if it is
> not.
> 
> I am running the latest linus 2.6.29-rc2 git kernel together with the
> master branch of the ext4 git tree announced here a couple of days ago.
> 
> Yesterday evening, all processes accessing /home which is formatted as
> ext4 (created as ext4 under 2.6.26 with the ext4 patches applied, not
> converted from ext3) were stuck in 'D' state and top showed both cores
> of the core2 CPU in 100% Waiting state. Everything not accessing /home
> was responsive. To eliminate a physical problem I ran a SMART self-test
> on the drive containing /home and it passed with no errors. / is also
> etx4, but was converted from ext3. There were no kernel messages, just
> the hung processes. The system would not reboot normally (because of the
> processes in 'D' state), but following sysrq sync, mount r/o and reboot,
> the filesystem showed as clean when restarted. To be sure, the first
> thing I did was to unmount it and manually ran fsck -f and that did not
> report any problems. 

If this happens again, could you use sysrq-l and capture resulting the
stack backtraces?  That would help determine what parts of the kernel
are responsible.

Regards,

							- Ted

  reply	other threads:[~2009-01-19 12:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-19  6:47 All processes accessing etx4 partition stuck in 'D' state Graham Murray
2009-01-19 12:43 ` Theodore Tso [this message]
2009-02-10 19:57   ` Graham Murray
2009-02-10 20:02     ` Eric Sandeen

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=20090119124305.GB7598@mit.edu \
    --to=tytso@mit.edu \
    --cc=graham@gmurray.org.uk \
    --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).