From: Jakob Haufe <sur5r@sur5r.net>
To: linux-ext4@vger.kernel.org
Subject: Re: online resize of ext4 hung (3.2.51 / 1.42.5)
Date: Sat, 26 Oct 2013 22:51:24 +0200 [thread overview]
Message-ID: <20131026225124.5fcfd7b0@samsa> (raw)
In-Reply-To: <20131025235745.GA2448@thunk.org>
[-- Attachment #1: Type: text/plain, Size: 862 bytes --]
On Fri, 25 Oct 2013 19:57:45 -0400
Theodore Ts'o <tytso@mit.edu> wrote:
> 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.
As the log was most probably too big to pass majordomo, i've put it here:
http://permalink.sur5r.net/1/linux-3.2.51-resize2fs-1.42.5-hung-sysrq-t.log
Please tell me whether you need anything beyond that (ssh access would be
possible) or whether I can put that machine back to production.
After a forced reboot, will an "fsck -f" be sufficient or should I create a
new filesystem? It was a newly set up backup target so I could scrap it if
necessary.
Cheers,
Jakob
--
ceterum censeo microsoftem esse delendam.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-10-26 20:51 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
2013-10-26 20:51 ` Jakob Haufe [this message]
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=20131026225124.5fcfd7b0@samsa \
--to=sur5r@sur5r.net \
--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).