From: Theodore Ts'o <tytso@mit.edu>
To: Jakob Haufe <sur5r@sur5r.net>
Cc: linux-ext4@vger.kernel.org
Subject: Re: online resize of ext4 hung (3.2.51 / 1.42.5)
Date: Fri, 25 Oct 2013 19:57:45 -0400 [thread overview]
Message-ID: <20131025235745.GA2448@thunk.org> (raw)
In-Reply-To: <20131025220632.62b4f9b3@samsa>
On Fri, Oct 25, 2013 at 10:06:32PM +0200, Jakob Haufe wrote:
>
> I can leave the machine sitting around for another day or maybe two, so if
> it's necessary to extract more information from somewhere, please tell me.
Can you run "echo t > /proc/sysrq-trigger" and send the output from
the console (or from dmesg)? Or otherwise trigger sysrq-t? This will
show the stacks of all of the processes, which would be useful to
figure out what might be happening.
Thanks,
- Ted
next prev parent reply other threads:[~2013-10-25 23:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 20:06 online resize of ext4 hung (3.2.51 / 1.42.5) Jakob Haufe
2013-10-25 23:57 ` Theodore Ts'o [this message]
2013-10-26 20:51 ` Jakob Haufe
2013-10-27 6:08 ` Theodore Ts'o
2013-10-28 14:39 ` Jakob Haufe
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=20131025235745.GA2448@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sur5r@sur5r.net \
/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).