From: Markus <M4rkusXXL@web.de>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Deadlock?
Date: Mon, 13 Feb 2012 12:17:28 +0100 [thread overview]
Message-ID: <3125411.WeeEOF8PnR@f209> (raw)
Hi!
I noted some kind of deadlock, where I was not able to write to the raid6,
while writing to each disk would still work.
This caused many processes to "wait" in d-state, thus making it impossible to
unmount, cleanly reboot, sync, ...
So I enabled the detection of hung tasks and this deplock option.
After running a 3.2.2 for about 5 days:
http://pastebin.com/gy1kaYmS
I dont know if its a bug or nothing. Or if it has anything to do with my
problem as there was no hungtask detected and the raid still seems to work.
Can anybody enlight me?! ;)
Markus
next reply other threads:[~2012-02-13 11:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 11:17 Markus [this message]
2012-02-13 17:37 ` Deadlock? Jack Stone
2012-02-14 12:47 ` Deadlock? Jan Kara
2012-02-15 11:42 ` Deadlock? Markus
2012-02-14 3:16 ` Deadlock? Paul Hartman
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=3125411.WeeEOF8PnR@f209 \
--to=m4rkusxxl@web.de \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.