Re: online resize of ext4 hung (3.2.51 / 1.42.5)

[Jakob Haufe <sur5r@sur5r.net>]

[-- 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 --]