From: Claudio Martins <ctpm@ist.utl.pt>
To: Nohez <nohez@cmie.com>
Cc: Mark Fasheh <mark.fasheh@oracle.com>, linux-kernel@vger.kernel.org
Subject: Re: OCFS2 Filesystem inconsistency across nodes
Date: Wed, 15 Feb 2006 21:42:47 +0000 [thread overview]
Message-ID: <200602152142.48028.ctpm@ist.utl.pt> (raw)
In-Reply-To: <Pine.LNX.4.33.0602152244050.3591-100000@mars.cmie.ernet.in>
On Wednesday 15 February 2006 17:50, Nohez wrote:
>
> Now started bonnie++ on one node while the same volume on the other node
> is mounted and is in quiescent stage. Its been more than 5 hours now
> and both the nodes are up & running. Seeing some very high load of >8 at
> times on the node running bonnie++. Test node has 4GB RAM and bonnie++
> is creating files of 8GB to test IO performance. Will start bonnie++
> on both the nodes concurrently later.
>
Nice. It'll be interesting when you start concurrent tests. I think the last
fixes from -mm made it better, but I'm still getting DLM errors and processes
hung in D state when using tar concurrently reading kernel trees on 3 nodes.
I'd like to know if you'll get the same or not.
I'll be sending kernel messages and a more complete report later this
evening.
Regards
Claudio
next prev parent reply other threads:[~2006-02-15 21:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 5:36 Claudio Martins
2006-02-10 6:46 ` Mark Fasheh
2006-02-10 7:20 ` Claudio Martins
2006-02-11 5:40 ` Claudio Martins
2006-02-13 22:26 ` Mark Fasheh
2006-02-14 0:00 ` Claudio Martins
2006-02-14 6:16 ` Claudio Martins
2006-02-14 20:19 ` Mark Fasheh
2006-02-15 3:17 ` Claudio Martins
2006-02-15 17:50 ` Nohez
2006-02-15 21:42 ` Claudio Martins [this message]
2006-02-14 12:17 ` Jan Kara
[not found] ` <20060210054958.GG4755@ca-server1.us.oracle.com>
2006-02-10 7:11 ` Claudio Martins
2006-02-13 15:08 Nohez
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=200602152142.48028.ctpm@ist.utl.pt \
--to=ctpm@ist.utl.pt \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
--cc=nohez@cmie.com \
/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