From: Heiko Nardmann <heiko.nardmann@itechnical.de>
To: linux-kernel@vger.kernel.org
Subject: Q: dlm_recoverd takes 100%
Date: Tue, 28 Aug 2012 10:54:58 +0200 [thread overview]
Message-ID: <503C8762.5070607@itechnical.de> (raw)
Hi together,
maybe someone can give me a hint which ML to contact (if I am wrong here)?
In a two-node cluster system I see 'dlm_recoverd' taking 100% time of
one cpu for around 6 minutes. Here is small excerpt from a 'top' output
during that period:
top - 10:51:01 up 3 days, 17:21, 5 users, load average: 10.19, 5.39, 2.76
Tasks: 536 total, 3 running, 533 sleeping, 0 stopped, 0 zombie
Cpu(s): 1.2%us, 6.6%sy, 0.0%ni, 92.1%id, 0.1%wa, 0.0%hi, 0.0%si,
0.0%st
Mem: 12183344k total, 11827540k used, 355804k free, 160332k buffers
Swap: 14417912k total, 0k used, 14417912k free, 8299364k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
3121 root 20 0 0 0 0 R 100.0 0.0 3:36.15 dlm_recoverd
The cluster nodes use a shared SAN (GFS2). The second node has been
rebooted while I experience this behaviour. The real problem is that my
application is unable to open a file on the SAN for these 6 minutes.
After the reboot of the second node all is fine again and the
application succeeds in opening the file. So I am not sure what can
cause those two symptoms.
Thanks in advance for any hint!
Kind regards,
Heiko
reply other threads:[~2012-08-28 8:55 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=503C8762.5070607@itechnical.de \
--to=heiko.nardmann@itechnical.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome