lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20131026225124.5fcfd7b0@samsa>
Date: Sat, 26 Oct 2013 22:51:24 +0200
From: Jakob Haufe <sur5r@...5r.net>
To: linux-ext4@...r.kernel.org
Subject: Re: online resize of ext4 hung (3.2.51 / 1.42.5)
On Fri, 25 Oct 2013 19:57:45 -0400
Theodore Ts'o <tytso@....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.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists