From: "Lluís Batlle i Rossell" <viric@viric.name>
To: reiserfs-devel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: More reiserfs hangs, easy to reproduce (Sheevaplug)
Date: Sun, 10 Jun 2012 16:27:25 +0200 [thread overview]
Message-ID: <20120610142724.GA2039@vicerveza.homeunix.net> (raw)
Hello,
I had since the latest 2.6 kernels lockups in a sheevaplug computer (without
swap), when it reached OOMK conditions. The machine was in such a deadlock that
it only answered to sysrq request through the serial console. Almost every OOMK
caused this, so once you reproduce an OOMK, I think it will almost sure hang the
system. The lock looks related to swapping in read-only pages of programs.
As I recently experienced reiserfs lockups in a desktop pc
(http://www.spinics.net/lists/reiserfs-devel/msg03157.html), I wondered if those
OOMK lockups could happen due to the reiserfs of /. So I moved / to ext4, and
all locks disappeared. OOMK works fine now.
So I'm definitely leaving reiserfs due to the deadlocks; a pity, because it
served very well to me for many years. I'd be glad to use it again with fixed
deadlock troubles.
If it's of help of anyone, here is the log (since just before the OOMK) taken by
netconsole, linux 3.4.1, and with some sysrq dumps. Since the OOMK message
appears, the machine answers to nothing but sysrq requests.
The log:
http://viric.name/tmp/hang/sheevaplug-hang1.txt.gz
Regards,
Lluís.
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2012-06-10 14:27 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=20120610142724.GA2039@vicerveza.homeunix.net \
--to=viric@viric.name \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@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).