From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] 2.6.37 - GFS2 trouble
Date: Thu, 13 Jan 2011 15:51:59 +0100 [thread overview]
Message-ID: <20110113145159.GA13573@pcnci.linuxbox.cz> (raw)
In-Reply-To: <1294650398.2450.3.camel@dolmen>
> Quotad is often the first victim of any slow down or problem on GFS2
> since it runs periodically (even if you are not using quotas, it also
> looks after statfs too).
>
> So I can't tell directly from that information what is wrong. I'd
> suggest taking glock dumps (via debugfs) as a first step. Grabbing
> backtraces of the glock_workqueue and other processes using gfs2 is
> probably the next step, and if that fails to point the way, the gfs2
> tracepoints are the next thing to look at,
Hello Steven,
Thanks a lot for Your reply and sorry for mine late one. I haven't been able
to reproduce the problem yet, now I'm running 2.6.37 without problems.
When it happens again, I'll dump locks and report again.
Have a nice day!
nik.
>
> Steve.
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava
tel.: +420 596 603 142
fax: +420 596 621 273
mobil: +420 777 093 799
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: servis at linuxbox.cz
-------------------------------------
prev parent reply other threads:[~2011-01-13 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-09 21:06 [Cluster-devel] 2.6.37 - GFS2 trouble Nikola Ciprich
2011-01-10 9:06 ` Steven Whitehouse
2011-01-13 14:51 ` Nikola Ciprich [this message]
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=20110113145159.GA13573@pcnci.linuxbox.cz \
--to=extmaillist@linuxbox.cz \
/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).