From: Russell Coker <russell@coker.com.au>
To: linux-btrfs@vger.kernel.org
Subject: Debian 3.14.13-2 lockup
Date: Mon, 18 Aug 2014 17:42:27 +1000 [thread overview]
Message-ID: <3745579.iqlhOmMKnP@xev> (raw)
[-- Attachment #1: Type: text/plain, Size: 632 bytes --]
I've attached the dmesg output from a system running Debian kernel 3.14.13
which locked up. Everything which needed to write to disk was blocked. The
dmesg output didn't catch the first messages which had scrolled out of the
buffer. As the disk wasn't writable there was nothing useful in
/var/log/kern.log .
As an aside one reason for using tmpfs for /tmp is that when the root
filesystem has a problem bash filename completion still works. I lost a
precious root shell on that system because I pressed TAB and bash hung.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
[-- Attachment #2: dmesg.txt.gz --]
[-- Type: application/gzip, Size: 12038 bytes --]
reply other threads:[~2014-08-18 7:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3745579.iqlhOmMKnP@xev \
--to=russell@coker.com.au \
--cc=linux-btrfs@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).